Difference between revisions of "PCD Profile Rosetta Terminology Mapping Overview"

From IHE Wiki
Jump to navigation Jump to search
(c)
m (c)
Line 48: Line 48:
 
:* [en.wikipedia.org/wiki/ISO/IEEE_11073 ISO/IEEE 11073-10101 Medical Device Communications - Nomenclature]
 
:* [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 76: 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'''
 +
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]
  
−
''<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. >''
 
−
 
−
-->
 
  
  
Line 87: Line 83:
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
−
 
−
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
 

Revision as of 15:48, 6 April 2011

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

<-- <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

Patient care devices and intermediaries or concentrators

Electronic Health Record 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

Profile Status: Trial Implementation

Documents:

RTM Document Page

Underlying Standards:

  • [en.wikipedia.org/wiki/ISO/IEEE_11073 ISO/IEEE 11073-10101 Medical Device Communications - Nomenclature]
  • HL7


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=49793"