Clinical Mapping
Clinical Mapping Profile supports the need of systems to translate codes from one terminology to another to support exchange of information between different systems.
Summary
Translations supported in the Clinical Mapping Profile are often needed at workflow boundaries where concepts used in one workflow have different names than those in another workflow. For example, in reporting device information to an EMR system, the device vendor may wish to capture device measurements of vital signs using internationally recognized terminologies provided by those devices, but the EMR may need to report these measurements using different terminologies to support local requirements. Another example would be for cases where data captured to support clinical activity for diagnosis or treatment must then be used to facilitate charge capture processes.
There are two ways that mappings can be done. The system doing the mapping can obtain the information on how to map individual terms as needed (e.g., through a query to a terminology mapper), or it can obtain data describing how the mapping should be done for all terms at a single point in time (e.g., startup). The former capability supports all terminology mapping needs, but may have a performance penalty when a large number of mappings need to be performed. The latter capability works in cases where the number of terms to be mapped is small, and the rules by which the mapping is performed are well defined.
Benefits
<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile. If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>
Details
<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>
<If the user might be familiar with the mechanisms used by the profile, you can mention them here. E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>
<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>
Systems Affected
- Personal Health Monitoring Devices
- EMRs and Other Health IT Systems
- Billing Systems
Actors & Transactions:
<Insert an actor-transaction diagram, and or list of Content Definitions>
Specification
Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>
Documents:
<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>
Underlying Standards:
<list all the standards on which the profile is based; if possible with links to sources>
See Also
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
Related Profiles
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>
Consumer Information
The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>
Implementer Information
The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>
Reference Articles
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >
This page is based on the Profile Overview Template