the present invention offers a unique approach to the selection and localization of clinical structured content ( e . g ., evidence - based structured content ) in order to facilitate the rapid development and regular update of these structures . an implementation will be described with reference to fig1 - 15 . referring to fig1 , embodiments of the present invention may facilitate the rapid development of clinical content structures , such as evidence - based order sets , for use in the practice of delivering patient care . generally speaking , an information provider , which may be an organization , team , third - party supplier , and so on , monitors the state of the evidence for selected clinical situations and produces evidence overviews that suggest certain practices . this typically includes review of medical journal articles and publications , but also may include reviewing unpublished studies , internal reviews and data aggregation , and the like . in some embodiments , there may be one , two , or more information providers . this evidence - based content is used by the information provider to construct a superset of order sets that are suggested by the evidence . these order sets are useful in their own right , and to provide further advantages in the use of such evidence and order sets ( and / or in use of other types of data ), embodiments of the present invention provide an environment for the end user ( typically one or more medical practitioners ) to review the suggested orders in a collaborative setting and make changes to reflect the local availability of order items and common practice , and to then quickly integrate the localized content into healthcare application from various vendors . as shown in the figure , in one embodiment , medical evidence 101 is used in an evidence synthesis process 102 to generate aggregated evidence 103 as well as default order sets 104 . the synthesis 102 may include comparing or reviewing evidence that was considered in the past , as well as new evidence , to form a synthesis of available evidence . the default order sets are order sets that are generated as a result of the synthesis 102 of the evidence 101 . the default order sets 104 may be in a standard term vocabulary 105 as described further herein . the default order sets 104 are provided in an authoring environment , shown in the diagram as the authorspace authoring environment 120 . the authoring environment 120 allows a practice team 106 , such as a hospital practice team to review and customize the default order sets 104 . this may involve extensive review by a number of people , by all relevant practitioners within a facility , or by a selected group or committee of practitioners . the result of the customization process 106 is a localized order set , stored and maintained within the authoring environment 120 . the localized order set 107 may be unchanged from the default order set 104 or may be modified as a result of review and modification during the customization process 106 . following completion of the review , the localized order set may be transformed 109 into a format suitable for a “ target ” health information technology ( hit ) system that is used by the practitioners in question . for example , the target hit system may be the hit system for a hospital , medical facility , or doctor &# 39 ; s office the transformation 109 makes use of the standard term vocabulary 105 used in creating and storing the default order sets 104 as well as information about the target hit system 108 . this information may include a target hit term catalog , which is information about the terms used or expected by the target hit system . the localized order set 107 is transformed 109 into the transformed , localized order set 110 , preferably into a format that will allow the transformed , localized order set 110 to be imported easily into the target hit system . it should be understood that the techniques described with respect to fig1 are applicable to any sort of clinical content , including without limitation order sets , plans of care , rules ( e . g ., rules for alerting ), alerts , protocols , performance measures , and / or structured documentation . here , order sets may represent a collection of orders and notations that are relevant to treating a given condition under a given set of circumstances based upon current evidence . plans of care refers to plans developed with health professionals that identify treatment needs , goals , and objectives of a participant based on clinical assessments , and may provide strategies for meeting goals and objectives and evaluating participant &# 39 ; s progress . rules and alerts refers to guidelines that show how evidence may be translated into alerts and / or reminders within electronic medical record systems . performance measures refers to a process or outcome that addresses healthcare quality and safety . structured documentation refers to documentation of a patient &# 39 ; s physical structure as may be included in medical records . the authored content may include combinations of these , and may also include other information , such as institutional data , policies , medical records , and meta data , which may include links to relevant documentation ( e . g ., evidence or practice patterns ). referring to fig2 , a method for use of an authoring environment , for example by a user is shown . in one embodiment , a medical practitioner , group of practitioners , and / or institution may begin by determining the medical condition or situation that requires clinical content , such as an evidence - based order set 201 . this could be , for example , based on their current outcome information or based on information from a provider , for example the evidence - based forcaster , available from zynx health incorporated of los angeles , calif . after identifying the relevant health condition ( s ), the user may perform content navigation in the authoring environment to peruse and select the default content 202 available in their order set database 203 . the default order sets may be order sets from an information provider 203 or they may be from another suitable source , such as a related facility , or otherwise . they duplicate the default order set 204 , for example , copying it into one of the folders in their authoring environment . one or more users then may review the recommended orders against their local order catalog 205 and against local common practice patterns either individually or in a collaborative work session . ( it should be understood that many other usage scenarios are possible ). the user ( s ) can then edit the order set 207 , for example to localize it , perform an internal review 208 , and if desired , allow for a public or more general review 209 . the localized order set then may be approved and released 210 . the order set is exported 211 into the specific vendor format and vocabulary for the hit application environment . the order set is then integrated 212 into the live hit application environment . again , it should be understood , that while the example of fig2 is described with respect to order sets , embodiments of the invention may be applicable to any content that is agreed upon by a group and adopted and integrated into an information technology system . the system has particular applicability for use with clinical content , because such content typically is commented and agreed on by groups of practitioners within an office , institution ( e . g ., hospital , clinic , urgent care center , nursing home , group practice , emergency department , etc . ), health care network , and so on prior to adoption , and also may be useful in other types of environments that have similar needs , even outside of health care . referring to fig3 , in some implementations , the system can also include features to ensure that content remains up to date as time passes and new relevant information becomes available . how the changes in the evidence and practice affect the life cycle of an order set in one embodiment is depicted in the figure . initially , an information provider creates a new order set based on the evidence for a given situation 301 . the user then chooses to duplicate and localize same and releases it for use in their institution 302 . the medical evidence can change over time 303 and when that occurs , the information provider may update the order set and publish it into authoring environment 304 , for example as a new version of the order set . publishing the new version of the order set will trigger a notification to those users that duplicated the previous version 305 so that they can review the differences 306 , update their local version as needed 307 , release 308 , export 309 and integrate the new version into their healthcare application 310 . this process may be iterative 311 as the evidence changes over time . referring to fig4 , depending on the hit healthcare application , the target vocabulary of the final version of the file could be a standard vocabulary 403 ( which may be a national standard code , such as snomed , loinc , ndc &# 39 ; s , cpt4 , icd9 - cm , and so on ), a vendor vocabulary that spans vendor customers 404 , or a local catalog just for ( or specific to ) the location ( e . g ., hospital , clinic , urgent care center , nursing home , group practice , emergency department , healthcare network , or other facility ) in question 405 . a vocabulary mapping functionality 402 allows for the mapping of any of these to a standard term vocabulary 401 , which is used for storing and maintaining the order sets while they are in the authoring environment , and before they are transformed into the local format 403 , 404 , 405 . referring now to fig5 , separate working environments for each facility ( e . g ., hospital , clinic , urgent care center , nursing home , group practice , emergency department , etc .) may be supported . thus , an exemplary hospital , shown as hospital x , 504 can have a dedicated environment 507 . within such an environment ( e . g ., 507 ) users have access to the content they have localized and can define their own milestones and environmental preferences . the content and preferences defined in one environment , e . g ., 507 , may not be accessible to users in other environments ( e . g ., 505 - 506 ) as the authoring space may segregate content virtually 508 through its data structures . however , in some cases ( e . g ., when several hospitals are related through a common health network 501 , 502 , 503 ), access to environments of other users or institutions may be desirable . this can be provided through a mechanism in an authoring environment for the creation of related environments . where related environments 505 , 506 have been established , the environments of related hospitals 502 , 503 can be viewed by each other . if so configured , the related environments may allowed editing and commenting by users associated with a related environment , without the risk of content corruption . referring to fig6 , in a typical implementation , access to an environment is protected by unique logins and passwords , with associated access privileges . a user accessing an authoring environment typically may access content only in the manner that has been defined in their access profile . the figure shows four exemplary users , user a 603 , user b 604 , user c 605 , and user d 606 . all users 603 , 604 , 605 , 606 within an authoring environment 601 are members of what is called the base team 602 . base team membership allows the users “ view - only ” access to the full set of content in the environment . within an environment the end user can establish teams ( e . g ., specialty team x 607 , specialty team y 608 ) for the creation of content and within those teams the users may be granted rights based upon their role on that team . some users 605 may not be assigned to a content team but may just be allowed view rights in the authoring environment . referring to fig7 , once a user has accessed an embodiment of an authoring environment , the initial page encountered by the user may be the main page as depicted in the figure . on this page , a user can view general announcements or messages 701 , see individualized notifications regarding their environment or content 702 , see a list of the teams they are currently on 704 , access additional functionality they may have access to 703 or peruse content for editing or management 705 , 706 . since some users can access multiple environments the environment may be displayed on this page as well 707 . authoring and managing content . beyond environment administration there are two major functions with regard to content development in an embodiment of an authoring environment : the content library , editor , manager , review tool and global content editor . the content library is where the user can search for content to edit , customize or manage . this library may be located in the main screen as depicted in fig7 . this library is organized into primary folders based on the source of the content and then into sub - folders that have been categorized by the aforementioned content source . in every case there are at least two source folders , one for default content , for example as provided by a service provider , and one for the environment &# 39 ; s local content . if the user has rights to see other content sources ( e . g ., from communities , vendors , etc . . . . ) they would see source folders for them as well . the user can navigate the folders or can execute a search across the folders for specific content meta data . ( e . g ., reason , venue , author , status . . . ). once selected , a user can edit , manage , delete , duplicate , print or export a content item . referring to fig8 , general navigation from the main page is depicted in this exemplary embodiment . from the main page 801 , the user can perform content functions 805 or other activity functions 802 . activity functions may include environment management 803 which allows certain users to modify the preferences , milestones and storage organization of the environment and vocabulary management 804 , which allows the user to import local order catalogs and map them to standard terms . content functions include viewing content , editing content 806 and managing content 807 . referring to fig9 , the content editor is an application that allows the user to modify structured content . an exemplary embodiment of an order set content editor is depicted in the figure . this interface is designed to accommodate organizing healthcare activities , orders and reminders into a logical structure dictated by the content author . thus , the localization of the order set occurs in the order set editor . the editor displays the order set in a hierarchical structure with sections 902 and order items 903 . at the top of the editor is a collection of base functions that can be performed on the order set . these items are dynamic and can change depending on the order set in the editor . they include adding sections to the root level of the order set , removing flagged items , inserting external order sets , un - deleting removed items , and closing or checking the order set back in . while editing the order set , the user can select an item 902 , 903 in the order set structure and open a workspace 904 to edit the item . the user interface within the workspace is dynamic and changes depending on the nature of the item being edited . an example might be for a simple order item like a lab test where , e . g ., the workspace would open to allow the user to enter schedule information ( urgency , number of times per day , etc . . . . ) but for a medication order the details would include elements like dose , dose form , special instructions and others . the user can attach a reference to an item in the order set . the reference can either be evidence from an information provider or any other valid internet address . the order set editor also allows the user to attach internal notes and tasks to items in the order set . in one embodiment , when a user edits an order set it is checked out to that user and cannot be edited by another user until it has been checked back in . this is to ensure that two users do not edit the order set at the same time which would result in content corruption . when the user is in the order set editor each change is sent back to the server and stored in a binary cache file so that if the internet connection is lost the last changes are preserved and available when the user returns and edits the order set . using the content editor , a user can expand and contract the logical structure of the content and see the items with the links to evidence where applicable . for example , the user may open an item to modify it or may choose to add a new item . structured content can be represented in a number of ways . for example : a single orderable item like a lab test or medication may be represented by a pivot term , a reminder or free text narrative can be inserted in the content to explain something to the user executing the structured content in their workflow , and a protocol which is a pointer to another , separate content structure , can be used to nest structures together where necessary . in one embodiment , when a user chooses to add or edit an item , the editor opens up a unique interface feature , referred to as a workspace . the workspace graphically expands the area containing the item ; this expansion occurs in the display to accommodate the details required to populate all of the data that is unique and required for the type of item that is being modified . this action is referred to as opening a workspace . when the user is done making changes , the workspace is closed and the display reverts to the standard view of the item within the structure ( with appropriate modifications to reflect changes made to the data ). any item in the structure can be linked to evidence provided by an information provider or an external source ( e . g ., an internet url ) for reference at a later time . for example , if a user needs to link to evidence she can open the evidence browser which allows her to search for the evidence she feels supports the item in question . the user can also attach notes or tasks to an item in the structure . these notes and tasks are for the users of the authoring environment within the authoring environment and are not exported to the target system . when content is accessed with the content editor , the content is checked out to ensure that multiple authors are not trying to modify the same piece of content simultaneously . if one user attempts to edit a piece of content that has been checked out by another , a message is displayed explaining that the content is already checked out and shows the user name of the user who has it locked . during an edit session , the content editor streams every change made back to the server and those changes are saved to a ‘ check - out ’ file . should the user lose their internet connection , their changes are preserved and will be available the next time they edit that content item . the content remains in a checked out state and can only be edited by the user who was working on it at the time the connection was lost ( though administrative overrides or time - outs may be implemented to prevent “ permanent ” lock - out of an item ). when a user is done making changes they can save their changes and check in the content . referring to fig1 , a content manager allows the user to change how the content fits into its environment . for example , changes can be made to : the meta - data ( reason , venue , event , etc ) that the content item is linked to , the team that has rights to modify the content , when the content expires , the milestones that have been achieved relative to the content , the system status of the content in the authoring environment ( draft , review , released , retired ), and whether or not the content item is shown in the public view space for the environment . when a content item is created , either from scratch or via the duplication of an existing work , it is stamped with a unique id and a version number . this version number is fixed when the content is released in the content manager . if a user chooses to edit a released content item a new draft with the same unique id is created . when the new draft is released the content manager automatically retires the previous version and stamps the newly released content with the next version number . preferably , retired versions of content are saved and can be viewed as they existed at the time they were retired . if the user sets an expiration date for the content item in the content manager , the authoring environment notification system will alert the owner of the content when the expiration date arrives . the content item can be linked to meta - data tags that help the consuming healthcare application determine when to show the content to their user . the meta - data tags relate the content to certain conditions , procedures or symptoms , a venue or location , a patient event and a specific institution if applicable . the content review tool . the content review tool allows the user to review a content item and make remarks for the author . these reviews are kept with the draft version of the order set . the global content editor . the global content editor is a tool that allows a user to execute bulk search and replaces across all of the released content in their environment . this can be used where , e . g ., a particular item ( e . g ., a particular drug or treatment ) is determined to be hazardous and needs to be removed from all content items as soon as possible . using the global content editor the user can quickly remove or replace those items and quick release the resulting new versions of those content items . the notification manager . the notification manager is designed to notify the user when something happens that has relevance to them or a content item that they are responsible for . events that potentially trigger the notification manager include new releases of content items , expiration of content items , and relevant changes to source content or evidence . in one embodiment , the notification manager posts a notice in the user &# 39 ; s authoring environment home page and optionally email the notice to the email address listed in the user &# 39 ; s profile . exporting content . an embodiment of the authoring environment includes a database to provide awareness of the healthcare applications used by an institution and has the facility to map pivot codes to the relevant local or standard vocabularies required by those applications . when a user chooses to export a content item , the user is presented with a choice of predefined exports . in one embodiment , the authoring environment has a standard xml export format as well as the custom formats built for each system vendor . related environments . an embodiment of an authoring environment has the ability to relate environments to one another for the purposes of sharing content . in some cases it could be that the health network has a parent environment and each hospital in the network has a child environment . each child would be able to see content that was authored at the network level and visa versa . this also facilitates the notion of a content sharing community . still referring to fig1 , once the user has modified the order set in the order set editor , the user can then manage the definitive characteristics , the condition , the venue and event the order set is mapped to as well as change the status of the order set using the order set manager . for example , on the order set manager page the user has functions they can perform relative to the order set 1001 . these functions can very depending on the status of the order set . the characteristics of the order set 1002 are the things that define the order set . the user can add and update environment specific lifecycle events to the order set 1003 . the user can post a review of the order set from this page , or from the viewspace portal . in either case the reviews can be viewed from the page as well 1004 . all changes made to the order set are logged in the audit trail database . major changes may be displayed in the order set history list box on this page 1005 . from this page the user can also mark the order set as a protocol , which allows it to be virtually linked into other order sets , or publish the order set into the environment &# 39 ; s viewspace , which allows users who do not have access to the authoring environment to see the content on , for example , a reference website . referring to fig1 , in one embodiment , changing the status of an order set , for example using the order set manager of fig1 , has ramifications with respect to the life cycle of an order set . these statuses are schematically depicted in the figure . when an order set is initially duplicated from the default order set , or created as blank , the order set is assigned an id and has a status of draft 1102 . while in draft status , the order set can be edited . upon initial completion , the status of the order set can be changed to review 1103 , which disables editing and allows users to post reviews of the order set . the user can then change the status back to draft 1102 to make additional edits in response to the reviews , or update the status to released 1104 . when the order set is released , it is stamped with a version number and permanently locked . if the user should decide to edit the order set a new draft is created . when the new draft is ultimately released 1106 it is stamped with the next version number and the previously released version is automatically retired 1105 . preferably , retired versions of order sets are permanently stored for reference purposes . a user can abort a new draft without impacting a previously released version of the order set . referring to fig1 , once a user is done editing the order set and has released it , they export the order set . an exemplary embodiment of an export process is depicted in fig1 . in order to resolve the issue of portability of content , embodiments of the present invention have the ability to transform both the terms used in the definition of the order set and the structural format of the order set in order to make it consumable within any healthcare application . when the order set is exported from the authoring environment 1201 , the terminology is transformed 1202 by the vocabulary mapping functionality , as depicted with reference to fig4 , and the resulting order set is created in a standard structure 1203 . this structure may then be converted by a custom export engine 1204 . the result is an export structure 1205 that is in the format required by the vendor system using the terms from the users local catalog . it is noteworthy that depending on the healthcare application , the target vocabulary of the final version of the file could be a standard vocabulary 403 , a vendor vocabulary that spans vendor customers 404 , or a local catalog just for the hospital in question 405 . the vocabulary mapping functionality 402 allows for the mapping of any of these to the standard term vocabulary 401 . referring to fig1 , one or many users in a given environment may be assigned the privileges of the environment manager . this privilege allows the user to access the environment manager link on the main page in the activities section 703 ( fig7 ). the environment management functions are depicted in fig1 . once on the environment management page 1301 , the user can perform several functions relating to the management of their environment . these include user management 1302 , team management 1304 , environment preferences 1307 and integration options 1312 . user management 1302 allows the environment manager to add or modify users that have access to the environment 1303 . by adding the user to the environment , for example , they may give them view access on the base team in the authoring environment . team management 1304 allows the environment manager to create 1305 and manage 1306 teams . managing the team is where users with access to the environment are added to teams and given team specific privileges that relate to the content that is owned by the team in question . environment preferences 1307 is where many of the configurable options for the environment can be manipulated by the environment manager . storage management 1308 allows the environment manager to create and organize their folder structure for storing their localized content . milestone management 1309 allows the environment manager to create content life cycle milestones that will be used in the order set manager to measure local progress on order set development . catalog management 1310 allows the environment manager to add terms to authoring environment that are not in the standard catalog . these new terms can be accessed by any environment user while in the order set editor . notification management 1311 allows the environment manager to attach milestone notifications to users in the environment . integration 1312 is where the environment manager can create allowable exports that can be selected by the environments users when they choose to export an order set . each environment is associated with one or many healthcare application vendors by administrative client services personnel depending on what systems they have in their health network or hospital . these exports can be configured by associating export vocabularies with a given export so that the proper terms are populating the right format . vocabulary management functionality in the present invention is used to support the transformation of the localized content into a form that is consumable by the end user &# 39 ; s healthcare application . term mapping is the relating of identical terms in two distinct vocabularies fig1 illustrates an example of the concept of term mapping . in this case the standard term vocabulary 1401 has a term representing a ‘ complete blood count ’ lab test 1403 . the external vocabulary 1402 has a term ‘ cbc ’ 1404 that has the exact same meaning as the previously mentioned term in the standard term vocabulary . these two terms could then be mapped so that every time the user selects the ‘ complete blood count ’ term in the authoring environment that item can be expressed to the consuming application with the ‘ cbc ’ identifier so that it can be understood . referring to fig1 , an embodiment of a process used to import and map external vocabularies is depicted . the user may export a file from their healthcare application containing the terms from their orders catalog 1501 . the authoring environment &# 39 ; s vocabulary import function 1502 processes the file based upon parameters provided by the user and stores the external terms in a database 1503 relative to the user &# 39 ; s environment . at this point , the user may add or modify terms using the vocabulary maintenance functions 1504 . the bulk of the effort would be in the mapping of the external terms to the standard term vocabulary 1505 . using the authoring environment vocabulary mapping tool 1506 , the user would establish links 1507 between the stored external terms 1503 and the standard vocabulary terms 1505 . these links will later be used by the export vocabulary transformation engine 1508 to transform the standard terms in the order set structures into the term that can be understood by the user &# 39 ; s healthcare application . the invention may be implemented in digital electronic circuitry , or in computer hardware , firmware , software , or in combinations of them . apparatus of the invention may be implemented in a computer program product tangibly embodied in a machine - readable storage device for execution by a programmable processor ; and method steps of the invention may be performed by a programmable processor executing a program of instructions to perform functions of the invention by operating on input data and generating output . the invention may advantageously be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from , and to transmit data and instructions to , a data storage system , at least one input device , and at least one output device . each computer program may be implemented in a high - level procedural or object - oriented programming language , or in assembly or machine language if desired ; and in any case , the language may be a compiled or interpreted language . suitable processors include , by way of example , both general and special purpose microprocessors . generally , a processor will receive instructions and data from a read - only memory and / or a random access memory . storage devices suitable for tangibly embodying computer program instructions and data include all forms of non - volatile memory , including by way of example semiconductor memory devices , such as eprom , eeprom , and flash memory devices ; magnetic disks such as internal hard disks and removable disks ; magneto - optical disks ; and cd - rom disks . any of the foregoing may be supplemented by , or incorporated in , specially - designed asics ( application - specific integrated circuits ). a number of embodiments of the present invention have been described . nevertheless , it will be understood that various modifications may be made without departing from the spirit and scope of the invention .