PCD Profile Rosetta Terminology Mapping Overview: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older edit
Jrhoads (talk | contribs)
editor
1,861 edits
new
PaulSherman (talk | contribs)
6,675 edits
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
''Rosetta Terminology Mapping (RTM) gives a vendor-neutral harmonized mapping for patient care device observations based on the ISO/IEEE 11073 Medical Device Communications (MDC) Nomenclature''
'''Rosetta Terminology Mapping (RTM)''' gives a vendor-neutral harmonized mapping for patient care device observations based on the ISO/IEEE 11073 Medical Device Communications (MDC) Nomenclature


__TOC__
__TOC__
Line 18: Line 18:
:*Reduces effort and error in mapping device data from multiple vendors for system interfacing. Formerly this was a new endeavor for every distinct pair of systems interfaced.
:*Reduces effort and error in mapping device data from multiple vendors for system interfacing. Formerly this was a new endeavor for every distinct pair of systems interfaced.


''<List the key benefits the profile provides (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>''
==Details==
 
The primary purpose of the Rosetta Terminology Mapping (RTM) profile is to harmonize the use of existing ISO/IEEE 11073-10101 nomenclature terms by systems compliant with IHE PCD profiles. The RTM profile also specifies the correct units-of-measure and enumerated values permitted for each numeric parameter to facilitate safe and interoperable communication between devices and systems.


==Details==
The Rosetta Table also is designed to serve as a temporary repository that can be used to define new nomenclature terms that are currently not present in the ISO/IEEE 11073-10101 nomenclature. Based on our experience to date, well over 100 new terms will be required, principally in the area of ventilator and ventilator settings. This could also serve as a framework for adding and reconciling new terms to support the IEEE 11073 ‘Personal Health Devices’ initiative.


<--
The repository is in the form of XML files.
''<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.>''
This profile specifies content. It does not specify any actors or transactions.


''<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==
==Systems Affected==


Line 36: Line 35:


Alarm Disseminating Systems
Alarm Disseminating Systems
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''


==Specification==
==Specification==
Line 48: Line 46:
'''Underlying Standards:'''
'''Underlying Standards:'''


:* [http://11073.org | ISO/IEEE 11073-10101 Medical Device Communications - Nomenclature]
:* [http://en.wikipedia.org/wiki/ISO/IEEE_11073 ISO/IEEE 11073-10101 Medical Device Communications - Nomenclature]
:* [http://www.hl7.org HL7]
:* [http://www.hl7.org HL7]
:* ...


<!--
 
 
==See Also==
==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'''


'''Related Profiles'''
[[PCD Profile DEC Overview | Device Enterprise Communication]] requires the use of RTM for parameter identification.


<!--
''<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.>''
''<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.''




Line 78: Line 71:


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>''
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'''
'''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. >''
Medical device interoperability and the Integrating the Healthcare Enterprise (IHE) initiative
JG Rhoads, T Cooper, F Fuchs, P Schluter… - AAMI IT Horiz, 2010, Pp. 22-27 -
[http://www.aami.org/publications/ITHorizons/2010/21-27_MDI_Rhoads.pdf PDF]


-->




Line 89: Line 84:


[[Category:Profiles]]
[[Category:Profiles]]
 
[[Category:PCD Profile]]
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
[[Category:HL7v2]]

Latest revision as of 13:36, 24 July 2017

Rosetta Terminology Mapping (RTM) gives a vendor-neutral harmonized mapping for patient care device observations based on the ISO/IEEE 11073 Medical Device Communications (MDC) Nomenclature

Summary

Rosetta Terminology Mapping is based on parameter lists submitted by several patient care device manufacturers, cross referenced to the MDC nomenclature standard. It allows communicating information systems to use a uniform method of identifying measurements and enumerations commonly sent by devices to information systems such as Electronic Health Record (EHR) systems.

Benefits

  • Reduces effort and error in mapping device data from multiple vendors for system interfacing. Formerly this was a new endeavor for every distinct pair of systems interfaced.

Details

The primary purpose of the Rosetta Terminology Mapping (RTM) profile is to harmonize the use of existing ISO/IEEE 11073-10101 nomenclature terms by systems compliant with IHE PCD profiles. The RTM profile also specifies the correct units-of-measure and enumerated values permitted for each numeric parameter to facilitate safe and interoperable communication between devices and systems.

The Rosetta Table also is designed to serve as a temporary repository that can be used to define new nomenclature terms that are currently not present in the ISO/IEEE 11073-10101 nomenclature. Based on our experience to date, well over 100 new terms will be required, principally in the area of ventilator and ventilator settings. This could also serve as a framework for adding and reconciling new terms to support the IEEE 11073 ‘Personal Health Devices’ initiative.

The repository is in the form of XML files.

This profile specifies content. It does not specify any actors or transactions.

Systems Affected

Patient care devices and intermediaries or concentrators

Electronic Health Record Systems

Alarm Disseminating Systems

Specification

Profile Status: Trial Implementation

Documents:

RTM Document Page

Underlying Standards:


See Also

Related Profiles

Device Enterprise Communication requires the use of RTM for parameter identification.


Reference Articles

Medical device interoperability and the Integrating the Healthcare Enterprise (IHE) initiative JG Rhoads, T Cooper, F Fuchs, P Schluter… - AAMI IT Horiz, 2010, Pp. 22-27 - PDF


This page is based on the Profile Overview Template

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