Search FHIR

ANS IG document core
0.1.0-snapshot - ci-build France flag

ANS IG document core - version de développement local (intégration continue v0.1.0-snapshot) construite par les outils de publication FHIR (HL7® FHIR® Standard). Voir le répertoire des versions publiées

: Example - Procedure avec Data Absent Reason - JSON Representation

Raw json | Download

{
  "resourceType" : "Procedure",
  "id" : "example-procedure-data-absent-reason",
  "meta" : {
    "profile" : [
      🔗 "https://interop.esante.gouv.fr/ig/document/core/StructureDefinition/fr-procedure-document"
    ]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Narratif généré : Procédure example-procedure-data-absent-reason</b></p><a name=\"example-procedure-data-absent-reason\"> </a><a name=\"hcexample-procedure-data-absent-reason\"> </a><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\"/><p style=\"margin-bottom: 0px\">Profil: <a href=\"StructureDefinition-fr-procedure-document.html\">Procedure - FR Procedure Document</a></p></div><p><b>identifier</b>: <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 \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:a1b2c3d4-e5f6-7890-abcd-ef1234567890</p><p><b>status</b>: Unknown</p><p><b>code</b>: <span title=\"Codes :\">Acte réalisé inconnu : utilisation de l'extension data-absent-reason avec code 'unknown'</span></p><p><b>subject</b>: <a href=\"Patient/exemple-patient\">Exemple Patient</a></p><p><b>performed</b>: Absent because : temp-unknown</p></div>"
  },
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:uuid:a1b2c3d4-e5f6-7890-abcd-ef1234567890"
    }
  ],
  "status" : "unknown",
  "code" : {
    "extension" : [
      {
        "url" : "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
        "valueCode" : "unknown"
      }
    ],
    "text" : "Acte réalisé inconnu : utilisation de l'extension data-absent-reason avec code 'unknown'"
  },
  "subject" : {
    "reference" : "Patient/exemple-patient",
    "display" : "Exemple Patient"
  },
  "_performedDateTime" : {
    "extension" : [
      {
        "url" : "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
        "valueCode" : "temp-unknown"
      }
    ]
  }
}