dok-beispiel-client-with-binary-pdf-example
type: DocumentReference
node role: treeRoot
id:
  v: dok-beispiel-client-with-binary-pdf-example
meta:
  profile:
    v: https://gematik.de/fhir/isik/StructureDefinition/ISiKDokumentenMetadaten
    l: ISiKDokumentenMetadaten
  security:
    system:
      v: http://terminology.hl7.org/CodeSystem/v3-ActReason
      l: v3-ActReason
    code:
      v: HTEST
text:
  status:
    v: generated
  div:
    v: Generated Narrative: DocumentReference dok-beispiel-client-with-binary-pdf-example Profile: Erforderliche Metadaten für Dokumentenaustausch in ISiK Security Label: test health data (Details: ActReason code HTEST = 'test health data') masterIdentifier: <a href="http://terminology.hl7.org/6.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 #xD;#xA;#xD;#xA;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: #xD;#xA;#xD;#xA;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.#xD;#xA;#xD;#xA;This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)/urn:oid:1.2.840.113556.1.8000.2554.58783.21864.3474.19410.44358.58254.41281.46340 status: Current type: Molekularpathologiebefund subject: Patient/PatientinMusterfrau securityLabel: normal content Attachments - ContentType Language Data Title Creation * application/pdf German (base64 data - 173,424 base64 chars) Molekularpathologiebefund vom 31.12.21 2020-12-31 23:50:50-0500 format: IHE Format Code set for use with Document Sharing: urn:ihe:iti:xds:2017:mimeTypeSufficient (Format aus MIME Type ableitbar) Contexts - Encounter FacilityType PracticeSetting * Encounter/FachabteilungskontaktNormal Krankenhaus Allgemeinmedizin
master identifier:
  system:
    v: urn:ietf:rfc:3986
    l: 3986
  value:
    v: urn:oid:1.2.840.113556.1.8000.2554.58783.21864.3474.19410.44358.58254.41281.46340
status:
  v: current
type:
  coding:
    system:
      v: http://dvmd.de/fhir/CodeSystem/kdl
      l: kdl
    code:
      v: PT130102
    display:
      v: Molekularpathologiebefund
subject:
  l: PatientinMusterfrau
  reference:
    v: Patient/PatientinMusterfrau
security label:
  coding:
    system:
      v: http://terminology.hl7.org/CodeSystem/v3-Confidentiality
      l: v3-Confidentiality
    code:
      v: N
content:
  attachment:
    content type:
      v: application/pdf
    language:
      v: de
    title:
      v: Molekularpathologiebefund vom 31.12.21
    creation:
      v: 2020-12-31T23:50:50-05:00
  format:
    system:
      v: http://ihe.net/fhir/ihe.formatcode.fhir/CodeSystem/formatcode
      l: formatcode
    code:
      v: urn:ihe:iti:xds:2017:mimeTypeSufficient
    display:
      v: Format aus MIME Type ableitbar
context:
  encounter:
    l: FachabteilungskontaktNormal
    reference:
      v: Encounter/FachabteilungskontaktNormal
  facility type:
    coding:
      system:
        v: http://ihe-d.de/CodeSystems/PatientBezogenenGesundheitsversorgung
        l: PatientBezogenenGesundheitsversorgung
      code:
        v: KHS
      display:
        v: Krankenhaus
  practice setting:
    coding:
      system:
        v: http://ihe-d.de/CodeSystems/AerztlicheFachrichtungen
        l: AerztlicheFachrichtungen
      code:
        v: ALLG