Difference between revisions of "PCD OID Management"
| Line 57: | Line 57: | ||
|1.3.6.1.4.1.19376.1.6.1.6 | |1.3.6.1.4.1.19376.1.6.1.6 | ||
|Parent OID for the IHE-PCD TF Supplement (Verson/Revision). | |Parent OID for the IHE-PCD TF Supplement (Verson/Revision). | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|1.3.6.1.4.1.19376.1.6.1.7 | |1.3.6.1.4.1.19376.1.6.1.7 | ||
Revision as of 12:29, 2 December 2011
Overview
Object Identifiers (OIDs) fill a need that comes up in many computing contexts, for identifiers that are guaranteed to be unique. With reliably unique identifier, you can be confident that your code for a measurement or a code set won’t collide with someone else’s. Unlike GUIDs or UUIDs, which are generated by a completely uncentralized process (using an algorithm that can run on any computer that is extremely unlikely to ever generate the same ID twice), OIDs are generated by a hierarchical network of aentities each of which is the ultimate authority for its own part of the tree.
IHE PCD now is one such authority.
There are a number of ISO Object Identifiers (OID) that are used in the PCD Technical Framework. This includes OIDs that relate directly to IHE PCD developed content (e.g., the registraton of a PCD-01 HL7 message profile, which requires an OID), as well as content from outside of IHE (e.g., OIDs identifying parameters defined in the ISO/IEEE 11073 standards).
References
CCITT, "Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)", CCITT Recommendation X.209, January 1988. ASN.1 is the original source of OIDs.
RFC 3061 - A URN Namespace of Object Identifiers. M. Mealling. A description of the general syntax and usage of OIDs.
IHE PCD OID
The following OID has been assigned to IHE PCD:
- 1.3.6.1.4.1.19376.1.6
OID Management
The generation and management of OIDs within the PCD will be coordinated with a general method for managing OIDs within the IHE, which is being worked on now. For the present, contact a Technical Committee Co-chair for assistance if you have a need or a question in this area.
General IHE-PCD OID Identifiers
| Template Identifier | Description |
| 1.3.6.1.4.1.19376.1.6 | Root OID for the PCD Domain. |
| 1.3.6.1.4.1.19376.1.6.1 | Root OID for the IHE-PCD Technical Framework [TF] (Verson) Volumes. |
| 1.3.6.1.4.1.19376.1.6.1.1 | Parent OID for the IHE-PCD TF (Verson/Revision) Volume 1 - Integration Profiles. |
| 1.3.6.1.4.1.19376.1.6.1.2 | Parent OID for the IHE-PCD TF (Verson/Revision) Volume 2 - Transactions (focused on Messages). |
| 1.3.6.1.4.1.19376.1.6.1.3 | Parent OID for the IHE-PCD TF (Verson/Revision) Volume 3 - Content Integration Profiles (focused on Syntax and Semantics). |
| 1.3.6.1.4.1.19376.1.6.1.4 | Parent OID for the IHE-PCD TF (Verson/Revision) Device Integration Profiles (focused on specific device types). (placeholder for future work - e.g., infusion pumps). |
| 1.3.6.1.4.1.19376.1.6.1.5 | Parent OID for the IHE-PCD TF (Verson/Revision) Clinical Integration Profiles. (placeholder for future work). |
| 1.3.6.1.4.1.19376.1.6.1.6 | Parent OID for the IHE-PCD TF Supplement (Verson/Revision). |
| 1.3.6.1.4.1.19376.1.6.1.7 | Parent OID for the IHE-PCD TF Trial Implementation (Verson/Revision). (e.g. . |
| 1.3.6.1.4.1.19376.1.6.1.8 | Parent OID for the PCD Actor (e.g., Device Observation Reporter [DOR]) |
| 1.3.6.1.4.1.19376.1.6.1.9 | Parent OID for the PCD Transaction (e.g., Communicate PCD Data [PCD-01]). |
| 1.3.6.1.4.1.19376.1.6.1.10 | Parent OID for the PCD Interaction (e.g., [ORU^R01]. |
OID Allocations
|}Under the IHE PCD arc, the existing assignments are:
| Template Identifier | Description |
| Specific IHE-PCD TF Volume 1 - Integration Profiles: | |
| 1.3.6.1.4.1.19376.1.6.1.6.2 | IHE Patient Care Devices Technical Framework, Volume 1: Integration Profiles (Version: 07-25-2011 Final Text) |
| Specific IHE-PCD TF Volume 2 - Transactions: | |
| 1.3.6.1.4.1.19376.1.6.2.2.1. | IHE Patient Care Devices Technical Framework, Volume 2: Transactions (Version: 08-12-2011 Revision 1.0 - Final Text |
| Specific IHE-PCD TF Supplements: | |
| 1.3.6.1.4.1.19376.1.6.1.6.2 | OID for the IHE-PCD TF Supplement - Alarm Communication Management [ACM] |
| 1.3.6.1.4.1.19376.1.6.1.6.2 | OID for the IHE-PCD TF Supplement - Waveform Content Message [WCM] |
| Trial Implementations | Specific IHE-PCD TF Trial Implementations: |
| Actors | Specific IHE-PCD Actors |
| Transactions | Specific IHE-PCD Transactions |
| 1.3.6.1.4.1.19376.1.6.1.9.1 | PCD-01: OID for Communicate PCD Data |
| 1.3.6.1.4.1.19376.1.6.1.9.1 | PCD-02: OID for Device to Enterprise Communications - Data Query |
| 1.3.6.1.4.1.19376.1.6.1.9.1 | PCD-03: OID for Point-of-care Infusion Verification - Communicate Infusion Order |
| 1.3.6.1.4.1.19376.1.6.1.9.1 | PCD-04: OID for Alarm Communications Management |
| 1.3.6.1.4.1.19376.1.6.1.9.1 | PCD-06: Alarm Communications Management |
| 1.3.6.1.4.1.19376.1.6.1.9.1 | PCD-07: Alarm Communications Management |
| 1.3.6.1.4.1.19376.1.6.1.9.1 | PCD-08: Alarm Communications Management |
| 1.3.6.1.4.1.19376.1.6.1.9.1 | PCD-09: Implantable Device - Cardiac Observation PCD-09 Communicate IDC Observations |
| Specific IHE-PCD Interactions | |
| 1.3.6.1.4.1.19376.1.6.1.10.1 | ORU^R01^ORU_R01: OID for the PCD Interaction ORU^R01. |
| 1.3.6.1.4.1.19376.1.6.1.10.1 | RRG^O16^RRG_O16: Point-of-care Infusion Verification RRG^O16^RRG_O16 Pharmacy/Treatment Give Acknowledgment
ISO/IEEE 11073 OIDsISO/IEEE 11073 nomenclature terms have OIDs from the arc 1.2.840.10004.1.1.1.0.0.1 See PCD SDO IEEE Coordination for a discussion of issues in the sonsistency of the ISO/IEEE 11073 OID usages. HL7 OID UseOIDs are used extensively as unique identifiers for codesets and similar artifacts, particularly in HL7 V3, both OIDs generated by the HL7 organization, as well as referencing OIDs from other organizations. HL7 allocates OIDs from the arc 2.16.840.1.113883 (joint-iso-itu-t.country.us.organization.hl7). They maintain a registry at http://www.hl7.org/oid/index.cfm. Additional Information |