Australian Digital Health Agency FHIR
1.2.0-ci-build - draft
Australian Digital Health Agency FHIR, published by Australian Digital Health Agency. This guide is not an authorized publication; it is the continuous build for version 1.2.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/AuDigitalHealth/mcv/ and changes regularly. See the Directory of published versions
<DocumentReference xmlns="http://hl7.org/fhir">
<id value="mbs-02"/>
<!-- Created DocumentReference from 'data in' Bundle | Post from Medicare repository to MHR -->
<!-- DocumentReference for ExplanationOfBenefit/mbs-02 -->
<meta>
<profile
value="http://ns.electronichealth.net.au/fhir/StructureDefinition/dh-documentreference-core-1"/>
</meta>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: DocumentReference mbs-02</b></p><a name="mbs-02"> </a><a name="hcmbs-02"> </a><a name="mbs-02-en-AU"> </a><p><b>masterIdentifier</b>: <a href="http://terminology.hl7.org/5.0.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt
This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid:
Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.
This OID may also be used in CD.codeSystem.">URI</a>/urn:uuid:79a8b5a5-1631-4eec-b031-815156c9a47b</p><p><b>identifier</b>: <a href="http://terminology.hl7.org/5.0.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt
This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid:
Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR.
This OID may also be used in CD.codeSystem.">URI</a>/urn:uuid:79a8b5a5-1631-4eec-b031-815156c9a47b</p><p><b>status</b>: Current</p><p><b>docStatus</b>: Final</p><p><b>type</b>: <span title="Codes:{https://healthterminologies.gov.au/fhir/CodeSystem/nctis-data-components-1 100.16644}">Medicare/DVA Benefits Report</span></p><p><b>category</b>: <span title="Codes:{https://healthterminologies.gov.au/fhir/CodeSystem/nctis-data-components-1 100.16644}">Medicare/DVA Benefits Report</span></p><p><b>subject</b>: <a href="Patient-mhr-field-sally.html">Sally FIELD Female, DoB: 1999-02-14 ( National unique individual identifier: Austalian Healthcare Identifier - Individual#8003608333563104 (use: official, ))</a></p><p><b>date</b>: 2017-12-04 01:02:00+1000</p><p><b>author</b>: <a href="Device-medicare-rs-01.html">Device: identifier = PAI-D: 8003640003000018; type = Medicare register system</a></p><p><b>custodian</b>: <a href="Organization-medicare-rs-operator.html">Organization Medicare Australia repository services operator</a></p><blockquote><p><b>content</b></p><h3>Attachments</h3><table class="grid"><tr><td style="display: none">-</td><td><b>Language</b></td><td><b>Url</b></td></tr><tr><td style="display: none">*</td><td>English (Region=Australia)</td><td><a href="http://example.org/mhr/xds/mhd/Binary/e2c4db8a-7164-46c3-990a-d00cdaec348d">http://example.org/mhr/xds/mhd/Binary/e2c4db8a-7164-46c3-990a-d00cdaec348d</a></td></tr></table></blockquote><h3>Contexts</h3><table class="grid"><tr><td style="display: none">-</td><td><b>SourcePatientInfo</b></td><td><b>Related</b></td></tr><tr><td style="display: none">*</td><td>Identifier: IHI/8003608000228437</td><td><a href="http://example.org/mhr/xds/mhd/ExplanationOfBenefit/79a8b5a5-1631-4eec-b031-815156c9a47b">http://example.org/mhr/xds/mhd/ExplanationOfBenefit/79a8b5a5-1631-4eec-b031-815156c9a47b</a></td></tr></table></div>
</text>
<masterIdentifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:uuid:79a8b5a5-1631-4eec-b031-815156c9a47b"/>
</masterIdentifier>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:uuid:79a8b5a5-1631-4eec-b031-815156c9a47b"/>
</identifier>
<status value="current"/>
<docStatus value="final"/>
<type>
<coding>
<system
value="https://healthterminologies.gov.au/fhir/CodeSystem/nctis-data-components-1"/>
<code value="100.16644"/>
<display value="Medicare/DVA Benefits Report"/>
</coding>
</type>
<category>
<coding>
<system
value="https://healthterminologies.gov.au/fhir/CodeSystem/nctis-data-components-1"/>
<code value="100.16644"/>
<display value="Medicare/DVA Benefits Report"/>
</coding>
</category>
<subject>🔗
<!-- Assume local record number will be used here instead of IHI -->
<reference value="Patient/mhr-field-sally"/>
<identifier>
<type>
<coding>
<system value="http://terminology.hl7.org/CodeSystem/v2-0203"/>
<code value="NI"/>
<display value="National unique individual identifier"/>
</coding>
<text value="IHI"/>
</type>
<system value="http://ns.electronichealth.net.au/id/hi/ihi/1.0"/>
<value value="8003608833357361"/>
</identifier>
</subject>
<!-- Instant this DocumentReference was created from the uploaded the Bundle | resource -->
<date value="2017-12-04T01:02:00+10:00"/>
<author>🔗
<reference value="Device/medicare-rs-01"/>
</author>
<custodian>🔗
<reference value="Organization/medicare-rs-operator"/>
</custodian>
<content>
<!-- Assumption that a Binary of the original upload is persisted -->
<attachment>
<language value="en-AU"/>
<url
value="http://example.org/mhr/xds/mhd/Binary/e2c4db8a-7164-46c3-990a-d00cdaec348d"/>
</attachment>
</content>
<!-- additional instances of related are instantiated if the Bundle | resource has been split across a DB -->
<context>
<sourcePatientInfo>
<identifier>
<type>
<coding>
<system value="http://terminology.hl7.org/CodeSystem/v2-0203"/>
<code value="NI"/>
</coding>
<text value="IHI"/>
</type>
<system value="http://ns.electronichealth.net.au/id/hi/ihi/1.0"/>
<value value="8003608000228437"/>
</identifier>
</sourcePatientInfo>
<!-- RELATED RESOURCES - REFERENCING INDIVIDUAL RESOURCES ACROSS THE DB THAT MAKE UP THIS 'DOCUMENT' -->
<!-- The url identifier scheme used below is nonsense should be replaced with the real scheme. The nonsense convention is document identifier (i.e. Bundle.identifier or Resource.identifier) -->
<!-- There is no related reference for a Patient record as this is not persisted - MHR Master Patient record is maintained and when a view or other output is
generated that generation process is to generate a fresh Patient resource according to current data and business rules -->
<related>
<reference
value="http://example.org/mhr/xds/mhd/ExplanationOfBenefit/79a8b5a5-1631-4eec-b031-815156c9a47b"/>
<!-- identifier below is the value of ExplanationOfBenefit.identifier -->
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:uuid:79a8b5a5-1631-4eec-b031-815156c9a47b"/>
</identifier>
</related>
</context>
</DocumentReference>