Stream: australia
Topic: common hospital URNO systems?
Andrew Patterson (Jan 31 2019 at 09:37):
I don't suppose anyone has actually nailed down any standardised hospital identifier systems for any major Australian hospitals. i.e. for hospital X we put our urno identifiers into system http://myhospital/id/urno? In particular if any of the cerner ones have their FHIR interfaces switched on - what identifier systems are they using?
Andrew Patterson (Jan 31 2019 at 09:39):
I guess that most hospitals without an EMR have given it zero thought - so maybe looking for some examples in (quasi) use in Australia to start the conversations rolling
Andrew Patterson (Jan 31 2019 at 09:39):
@Brett Esler
Grahame Grieve (Jan 31 2019 at 10:41):
cerner interface is not that far along yet
Grahame Grieve (Jan 31 2019 at 10:42):
and we never had such a framework for identifiers before, so it seems a hard road to get one now
Brett Esler (Jan 31 2019 at 19:24):
best recommendation I have now is to use the Medical Record Number slice defined in Patient.identifier in AU Base
pasted image
http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-patient.html
the Identifier.type.coding set to MR - so identifies the identifier type; the Identifier.system is required but not explicitly defined. Depending on the scope of the URNO allocation there are a couple of schemes about to use ABN or HPIO to create a system url in case one is not explicitly defined; but would need to be careful with those to ensure global uniqueness (a variation of this scheme based on OID was documented in AU CDA implementation guidance)
@Rob Eastwood @David McKillop can you help locate details of using ABN or HPIO based system urls?
Andrew Patterson (Jan 31 2019 at 21:59):
Yep sorry @Grahame Grieve - wasn't meaning a framework.. Just literally need a identifier system for our local Major Hospital URNO - where I am constructing the FHIR on their behalf. Was hoping someone had already done the work for this particular hospital! I am not looking forward to the inevitable rounds of emails where I try to get them agree/understand what I am asking for
Andrew Patterson (Jan 31 2019 at 22:00):
@Brett Esler A ABN or HPIO system url sounds like a plan - I feel comfortable using that without having to run it past hundreds of committees - and then I can align to any 'official' FHIR systems they come up with as their EMR etc develops
Brett Esler (Jan 31 2019 at 22:27):
just be cautious with scope as since an ABN or HPIO scope is for the whole business or organisation; could be an issue if you start doing that across multiple domains of use e.g. multiple URN allocating systems ; or identifiers allocated for multiple purposes e.g. patient identifier; provider identifier - start to worry about overall uniqueness of system/value
Rob Eastwood (Feb 01 2019 at 00:09):
@Brett Esler, @Andrew Patterson & @David McKillop
Assuming that I have understood correctly, I believe that the following Agency hosted namespaces would be what you are after:
- http://ns.electronichealth.net.au/id/abn-scoped/medicalrecord/1.0
- http://ns.electronichealth.net.au/id/hpio-scoped/medicalrecord/1.0
Both resolve and have narrative regarding usage & associated OID content.
FYI - incidentally the parent page (http://ns.electronichealth.net.au/browse-identifiers.html) contains a listing of a number of other identifier namespaces
Brett Esler (Feb 01 2019 at 00:10):
thanks @Rob Eastwood that handles some of my concerns re scope
Andrew Patterson (Feb 01 2019 at 03:36):
thanks. noted re: scope.. for the agency hosted namespaces, if I have an UR_NO 1234 for hospital with HPIO XYZ
system = urn:ietf:rfc:3986 , value = http://ns.electronichealth.net.au/id/hpio-scoped/medicalrecord/1.0/XYZ/1234
or
system = http://ns.electronichealth.net.au/id/hpio-scoped/medicalrecord/1.0/XYZ, value = 1234
Andrew Patterson (Feb 01 2019 at 03:41):
I would very much prefer to have the UR_NO as a discrete number so second is preferably for me
Richard Townley-O'Neill (Feb 01 2019 at 03:54):
system = http://ns.electronichealth.net.au/id/hpio-scoped/medicalrecord/1.0/XYZ, value = 1234
is preferred
Last updated: Apr 12 2022 at 19:14 UTC