Difference between revisions of "PCD Profile Rosetta Terminology Mapping Overview"
PaulSherman (talk | contribs) |
PaulSherman (talk | contribs) |
||
| Line 85: | Line 85: | ||
[[Category:Profiles]] | [[Category:Profiles]] | ||
[[Category:PCD Profile]] | [[Category:PCD Profile]] | ||
| + | [[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:
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