Difference between revisions of "Clinical Mapping"

From IHE Wiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
=== This profile has been deprecated. ===
  
−
Clinical Mapping Profile supports the need of systems to translate codes from one terminology to another to support exchange of information between different systems.
+
replaced by [[Sharing Valuesets, Codes and Maps (SVCM)]]
−
 
 
−
__TOC__
 
−
 
 
−
==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.
 
−
 
 
−
[[Image:CMAP usecasediagram.png|450px|center]]
 
−
 
 
−
==Benefits==
 
−
* Significant time savings
 
−
* Data entry error reduction
 
−
* Consistency in practice to permit comparison and aggregation of data post-conversion
 
−
 
 
−
==Details==
 
−
A crosswalk is a mapping from one coding system to another in which concepts from the source coding system are mapped to concepts in the target code system. The simplest form of crosswalk is a lookup table. This form is often used to translate from local codes to codes from standard terminologies. Guidance on the concepts of input context and output context are provided in this profile that deal with factors affecting both the inbound and outbound sides of code translations. Additionally, CMAP supports access to individual transactions providing the opportunity for implementers to leverage features such as cacheing and refreshing of terminology maps that are provided by external services.
 
−
 
 
−
==Systems Affected==
 
−
* Personal Health Monitoring Devices
 
−
* EMRs and Other Health IT Systems
 
−
* Billing Systems
 
−
 
 
−
 
 
−
'''Actors & Transactions:'''
 
−
 
 
−
[[Image:CMAP_actortransaction.png|450px|center]]
 
−
 
 
−
==Specification==
 
−
 
 
−
'''Profile Status:''' [[Comments| Trial Implementation]] 
 
−
''<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.>''
 
−
 
 
−
<!--
 
−
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
−
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
−
-->
 
−
 
 
−
'''Underlying Standards:'''
 
−
 
 
−
 
 
−
''<list all the standards on which the profile is based; if possible with links to sources>''
 
−
<!--
 
−
:* [http://dicom.nema.org DICOM]
 
−
:* [http://www.hl7.org HL7]
 
−
:* ...
 
−
-->
 
−
 
 
−
==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.>''
 
−
 
 
−
<!--
 
−
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
 
−
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 
−
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 
−
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 
−
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 
−
-->
 
−
 
 
−
'''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]]
 
−
 
 
−
[[Category:Template]]
 

Latest revision as of 15:16, 20 November 2020

This profile has been deprecated.

replaced by Sharing Valuesets, Codes and Maps (SVCM)

Retrieved from "http://wiki.ihe.net/index.php?title=Clinical_Mapping&oldid=123484"