ProcedureExample
type: Procedure
node role: treeRoot
resource.id:
  value: ProcedureExample
resource.meta:
  meta.profile:
    value: https://fhir.hl7.at/elga/ediag/r4/StructureDefinition/at-elga-ediag-procedure
    index: 0
    link: https://fhir.hl7.at/elga/ediag/r4/StructureDefinition/at-elga-ediag-procedure
  meta.tag:
    index: 0
    coding.system:
      value: https://fhir.hl7.at/elga/ediag/r4/CodeSystem/at-ediag-codesystem-diagnose-type
    coding.code:
      value: relevant
    coding.display:
      value: currently relevant
domain resource.text:
  narrative.status:
    value: extensions
  narrative.div: Generated Narrative: Procedure ProcedureExample Profile: AT ELGA e-Diagnose Procedure Tag: currently relevant (Details: AT e-Diagnose Diagnose Typ code relevant = 'currently relevant') AT ELGA Reported (Fremdangabe): false status: Completed code: Coloskopie subject: Identifier: urn:oid:1.2.40.0.10.2.1.1.149/GH:oeLdSEb0l+8kSdJWjOYyYmnYki0= performed: 2026-04-20 09:30:00+0200 recorder: Identifier: <a href="http://terminology.hl7.org/7.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.40.0.34.99.4613.4 asserter: Identifier: <a href="http://terminology.hl7.org/7.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;Not…
domain resource.extension:
  index: 0
  extension.url:
    value: https://fhir.hl7.at/elga/ediag/r4/StructureDefinition/at-elga-ediag-reported
  extension.value boolean:
    value: false
procedure.status:
  value: completed
procedure.code:
  codeable concept.coding: http://snomed.info/id/73761001
    index: 0
    coding.system:
      value: http://snomed.info/sct
    coding.code:
      value: 73761001
    coding.display:
      value: Coloskopie
procedure.subject:
  reference.type:
    value: Patient
  reference.identifier:
    identifier.system:
      value: urn:oid:1.2.40.0.10.2.1.1.149
    identifier.value:
      value: GH:oeLdSEb0l+8kSdJWjOYyYmnYki0=
procedure.performed date time:
  value: 2026-04-20T09:30:00+02:00
procedure.recorder:
  reference.type:
    value: Practitioner
  reference.identifier:
    identifier.system:
      value: urn:ietf:rfc:3986
    identifier.value:
      value: urn:oid:1.2.40.0.34.99.4613.4
procedure.asserter:
  reference.type:
    value: Practitioner
  reference.identifier:
    identifier.system:
      value: urn:ietf:rfc:3986
    identifier.value:
      value: urn:oid:1.2.40.0.34.99.4613.4
procedure.note:
  index: 0
  annotation.text:
    value: Diagnostische Coloskopie. Histologiebefund ausständig