HL7AU - FHIR WG : HPI-O: Organisation Healthcare Provider Identifier

Created by Brian Postlethwaite on 14 Jun, 2016
  • HPI-O or HPIO for type/text?
  • type/coding/code/@value = 'XX' other options? 'NOI' as an AU extension (already approved for v2.8.2 or v2.9?)
  • constraints: value/@value - 16 digits; prefix 800362; Luhn check

Example:

<Organization>
    ...
    <identifier>
        
        <type> 
            <coding> 
                <system value="http://hl7.org/fhir/v2/0203"/>
                <code value="NOI"/>
                <display value="National Organization Identifier"/>
            </coding>
            <text value="HPI-O"/> 
        </type>
        <system value="http://ns.electronichealth.net.au/id/hi/hpio/1.0"/>
        <value value="8003627500000328"/>
        
        
   </identifier>
   ...
</organization>

Comments:

The HPI-O identifier is currently inadequate to meet Australian needs, because it has not been adopted at the level of granularity needed in most states. My understanding is that it may never be adopted in some states/organisations at the level of a hospital, potentially due to perceived/potential legal liabilities and penalties.  

What are the FHIR use cases for organisational identifiers?

How do we assess the required granularity of an 'organisation'?
Posted by eric.browne at 22 Jul, 2016 13:39

The proposal here is not to state when to represent the identifier, or what organizations must have one, but how it should be represented if it is decided to be included.

(Which is the same for the patient identifiers also)
Posted by brian_pos at 22 Jul, 2016 13:42

That sounds like a cart before a horse. 

  1. Why produce a profile for organisation which uses an identifier that won't work adequately?
  2. Why not produce a profile for an organisation which can adequately identify the organisation?
Posted by eric.browne at 22 Jul, 2016 13:51