Difference between revisions of "PCD Profile Rosetta Terminology Mapping Overview"
(begin) |
(new) |
||
| 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'' | ||
| + | __TOC__ | ||
| − | [[PCD_Profile_Rosetta_Terminology_Mapping]] | + | ==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. | ||
| + | |||
| + | <!-- | ||
| + | ''<Describe the profile in about a paragraph using user-oriented language. Focus on what it accomplishes for a user (i.e. the Use Cases). Don't get into how it works, leave that to the Details section.>'' | ||
| + | |||
| + | ''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about. Do not use an actor/transaction diagram here. Show your graphic to someone for 5 seconds (literally) and ask them what it's about. If what they say hits the main points in your summary paragraph, you have succeeded. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. .>'' | ||
| + | |||
| + | ''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>'' | ||
| + | --> | ||
| + | ==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. | ||
| + | |||
| + | ''<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== | ||
| + | |||
| + | <-- | ||
| + | ''<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:''' | ||
| + | |||
| + | [[PCD_Profile_Rosetta_Terminology_Mapping | RTM Document Page]] | ||
| + | |||
| + | '''Underlying Standards:''' | ||
| + | |||
| + | :* [http://11073.org | ISO/IEEE 11073-10101 Medical Device Communications - Nomenclature] | ||
| + | :* [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:Profiles]] | ||
| + | |||
| + | <noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude> | ||
Revision as of 15:34, 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.
<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
<-- <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:
Underlying Standards:
This page is based on the Profile Overview Template
<Delete this Category Templates line since your Profile page is no longer a template.>