AU Core Implementation Guide
0.3.0-ballot - R1 Australia flag

This page is part of the AU Core (v0.3.0-ballot: AU Core R1 Ballot 5) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions

: DocumentReference - Advance Care Plan, referenced by Provenance/signature example - JSON Representation

Page standards status: Informative

Raw json | Download


{
  "resourceType" : "DocumentReference",
  "id" : "acp",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p><b>Generated Narrative: DocumentReference</b><a name=\"acp\"> </a></p><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Resource DocumentReference &quot;acp&quot; </p></div><p><b>masterIdentifier</b>: <a href=\"http://terminology.hl7.org/5.3.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 \r\n\r\nThis 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: \r\n\r\nNote 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.\r\n\r\nThis OID may also be used in CD.codeSystem.\">Uniform Resource Identifier (URI)</a>/urn:uuid:1421b2d5-7e43-4414-93c5-d1db160e5513</p><p><b>identifier</b>: <a href=\"http://terminology.hl7.org/5.3.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 \r\n\r\nThis 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: \r\n\r\nNote 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.\r\n\r\nThis OID may also be used in CD.codeSystem.\">Uniform Resource Identifier (URI)</a>/urn:uuid:1421b2d5-7e43-4414-93c5-d1db160e5513</p><p><b>status</b>: current</p><p><b>docStatus</b>: final</p><p><b>type</b>: Advance Care Planning Document <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (nctis-data-components-1#100.16998)</span></p><p><b>category</b>: Advance Care Information <span style=\"background: LightGoldenRodYellow; margin: 4px; border: 1px solid khaki\"> (nctis-data-components-1#100.16975)</span></p><p><b>subject</b>: <a href=\"Patient-wang-li.html\">Patient/wang-li</a> &quot; WANG&quot;</p><p><b>date</b>: 3 Nov. 2019, 1:35:00 pm</p><p><b>author</b>: <a href=\"PractitionerRole-bobrester-bob-gp.html\">PractitionerRole/bobrester-bob-gp</a></p><p><b>authenticator</b>: <a href=\"PractitionerRole-bobrester-bob-gp.html\">PractitionerRole/bobrester-bob-gp</a></p><p><b>custodian</b>: <a href=\"Organization-bobrester-medical-center.html\">Organization/bobrester-medical-center</a> &quot;Bobrester Medical Center&quot;</p><p><b>description</b>: Mr. Li Wang's Advance Care Plan</p><blockquote><p><b>content</b></p><h3>Attachments</h3><table class=\"grid\"><tr><td style=\"display: none\">-</td><td><b>ContentType</b></td><td><b>Url</b></td><td><b>Hash</b></td></tr><tr><td style=\"display: none\">*</td><td>application/pdf</td><td><code>acp_attachment.pdf</code></td><td>(base64 data - 20 bytes)</td></tr></table></blockquote></div>"
  },
  "masterIdentifier" : {
    "system" : "urn:ietf:rfc:3986",
    "value" : "urn:uuid:1421b2d5-7e43-4414-93c5-d1db160e5513"
  },
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:uuid:1421b2d5-7e43-4414-93c5-d1db160e5513"
    }
  ],
  "status" : "current",
  "docStatus" : "final",
  "type" : {
    "coding" : [
      {
        "system" : "https://healthterminologies.gov.au/fhir/CodeSystem/nctis-data-components-1",
        "code" : "100.16998",
        "display" : "Advance Care Planning Document"
      }
    ]
  },
  "category" : [
    {
      "coding" : [
        {
          "system" : "https://healthterminologies.gov.au/fhir/CodeSystem/nctis-data-components-1",
          "code" : "100.16975",
          "display" : "Advance Care Information"
        }
      ]
    }
  ],
  "subject" : {
    🔗 "reference" : "Patient/wang-li"
  },
  "date" : "2019-11-03T12:35:00+10:00",
  "author" : [
    {
      🔗 "reference" : "PractitionerRole/bobrester-bob-gp"
    }
  ],
  "authenticator" : {
    🔗 "reference" : "PractitionerRole/bobrester-bob-gp"
  },
  "custodian" : {
    🔗 "reference" : "Organization/bobrester-medical-center"
  },
  "description" : "Mr. Li Wang's Advance Care Plan",
  "content" : [
    {
      "attachment" : {
        "contentType" : "application/pdf",
        "url" : "acp_attachment.pdf",
        "hash" : "IiZNlyLY4gyewfICeWhFe2NcDDw="
      }
    }
  ]
}