-
Notifications
You must be signed in to change notification settings - Fork 0
Frequently Asked Questions
HPI-O scoped identifiers enable exchange of an organisation's local identifiers for things like a patient medical record. It is preferable that an organisation uses their own local system identifier namespace but if that is not available then an organisation can add their HPI-O to construct a legal globally unique identifier system for their local identifiers.
The full list of available identifier namespaces can be found by browsing the ns.electronichealth.net.au identifier namespaces; there are several HPI-O scoped identifier namespaces available:
http://ns.electronichealth.net.au/id/hpio-scoped/accessionnumber/1.0
http://ns.electronichealth.net.au/id/hpio-scoped/dispense/1.0
http://ns.electronichealth.net.au/id/hpio-scoped/medicalrecord/1.0
http://ns.electronichealth.net.au/id/hpio-scoped/order/1.0
http://ns.electronichealth.net.au/id/hpio-scoped/prescription/1.0
http://ns.electronichealth.net.au/id/hpio-scoped/report/1.0
http://ns.electronichealth.net.au/id/hpio-scoped/service-provider-individual/1.0
There are three parts to the using an HPI-O-scoped identifier in FHIR. The ns.electronichealth.net.au namespace, the HPI-O, and the local identifier. When sent as an Identifier the ns.electronichealth.net.au namespace and the HPI-O are sent in the system:
<system value="http://ns.electronichealth.net.au/id/hpio-scoped/service-provider-individual/1.0/8003621566684455" />
With the local identifier sent in the value:
<value value="frankburns27" />
Altogether the identifier might look something like:
<identifier>
<type>
<coding>
<system value="http://hl7.org/fhir/v2/0203"/>
<code value="EI"/>
<display value="Employee number"/>
</coding>
<text value="Employee Number"/>
</type>
<system value="http://ns.electronichealth.net.au/id/hpio-scoped/service-provider-individual/1.0/8003621566684455" />
<value value="frankburns27" />
<assigner>
<display value="Test Medical Centre 123"/>
</assigner>
</identifier>
ABN-scoped identifiers enable exchange of an organisation's local identifiers for things like a patient medical record. It is preferable that an organisation uses their own local system identifier namespace but if that is not available then an organisation can add their ABN or ACN to construct a legal globally unique identifier system for their local identifiers.
The full list of available identifier namespaces can be found by browsing the ns.electronichealth.net.au identifier namespaces; there are two ABN-scoped identifier namespaces available:
http://ns.electronichealth.net.au/id/abn-scoped/medicalrecord/1.0
http://ns.electronichealth.net.au/id/abn-scoped/service-provider-individual/1.0
There are three parts to the using an ABN-scoped identifier in FHIR. The ns.electronichealth.net.au namespace, the ABN or ACN, and the local identifier. When sent as an Identifier the ns.electronichealth.net.au namespace and the ABN or ACN are sent in the system:
<system value="http://ns.electronichealth.net.au/id/abn-scoped/medicalrecord/1.0/004085616" />
With the local identifier sent in the value:
<value value="123456" />
Altogether the identifier might look something like:
<identifier>
<type>
<coding>
<system value="http://hl7.org/fhir/v2/0203"/>
<code value="MR"/>
<display value="Medical record number"/>
</coding>
<text value="Medical Record Number"/>
</type>
<system value="http://ns.electronichealth.net.au/id/abn-scoped/medicalrecord/1.0/004085616" />
<value value="123456" />
<assigner>
<display value="Test Hospital Org 1"/>
</assigner>
</identifier>