Difference between revisions of "Datatypes R2 Issue 94"
| Line 11: | Line 11: | ||
== Discussion == | == Discussion == | ||
| − | + | the proposed mechanism is | |
| + | |||
| + | |||
| + | |||
| + | A new unregistered scheme is proposed to address the situation where an HL7 Instance Identifier, comprised of a root and option extension, needs to be referenced as a single identifier. | ||
| + | |||
| + | Scheme: hl7ii this scheme name is suggested as it extends the hl7 conventional use with the "ii" specific use identifier. | ||
| + | |||
| + | Pattern String: root[:extension] this pattern allows for ready parsing of the id root and extension of the referred id | ||
| + | |||
| + | example: reference="urn:hl7ii:2.1.16.3.9.12345.2.39.3:ABC123" would refer to the Instance Identifier root="2.1.16.3.9.12345.2.39.3" extension="ABC123" | ||
| + | |||
| + | |||
== Status == | == Status == | ||
approved | approved | ||
Latest revision as of 04:54, 15 June 2007
== URL reference to an II ==
This is a standing issue about how to use a URL (such as in ED.reference) to refer to something that is identified by an II (such as Act.id).
Disposition
20070501 WGM: where a URI is required for referencing an II, the URI definition as used in ebXML specification should be used. Charlie/Doug 15-0-2
Discussion
the proposed mechanism is
A new unregistered scheme is proposed to address the situation where an HL7 Instance Identifier, comprised of a root and option extension, needs to be referenced as a single identifier.
Scheme: hl7ii this scheme name is suggested as it extends the hl7 conventional use with the "ii" specific use identifier.
Pattern String: root[:extension] this pattern allows for ready parsing of the id root and extension of the referred id
example: reference="urn:hl7ii:2.1.16.3.9.12345.2.39.3:ABC123" would refer to the Instance Identifier root="2.1.16.3.9.12345.2.39.3" extension="ABC123"
Status
approved
