Difference between revisions of "PCD OID Management"
ToddCooper (talk | contribs) m (Initial Version) |
m (→Overview) |
||
| Line 2: | Line 2: | ||
==Overview== | ==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). | 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== | ==IHE PCD OID== | ||
Revision as of 17:38, 29 June 2009
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
<Note: Discuss how PCD allocates and documents OID assignments>
OID Allocations
<Note: Indicate specific allocations of PCD OIDs; a la the ITI OID page listed below>
ISO/IEEE 11073 OIDs
<Note: Provide X73 OID arc examples and usage>
HL7 OID Use
<Note: Discuss how PCD uses OIDs w.r.t. HL7-based artifacts>