DSTU2

This page is part of the FHIR Specification (v0.0.82: (v1.0.2: DSTU 1). 2). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Provenance-example.json

Raw JSON ( canonical form )

General Provenance Example of provenance

{
  "resourceType": "Provenance",
  "id": "example",

  "text": {
    "status": "generated",
    "div": "<div>Authored on 8-Nov 2011 by Grahame Grieve. Content extracted from ISO-21090</div>"

    "div": "<div>procedure record authored on 27-June 2015 by Harold Hippocrates, MD Content extracted from Referral received 26-June</div>"

  },
  "target": [
    {
      "reference": "Patient/example/history/1"

      "fhir_comments": [
        "  \n    where possible, provenance targets should be version specific,\n    so that there is no ambiguity about which version of the \n    record this relates to\n   "
      ],
      "reference": "Procedure/example/_history/1"

    }
  ],
  "period": {
    "start": "2011-06-23"
  },
  "recorded": "2012-11-08T23:16:03+11:00",
  "reason": {
    "text": "Editing the FHIR Specification"

    "start": "2015-06-27"

  },
  "recorded": "2015-06-27T08:39:24+10:00",
  "reason": [
    {
      "coding": [
        {
          "system": "http://snomed.info/sct",
          "code": "3457005",
          "display": "Referral"
        }
      ],
      "text": "Accepting a referral"
    }
  ],

  "location": {
    "reference": "Location/2"

    "reference": "Location/1"

  },
  "policy": [
    "http://acme.com/fhir/Consent/25"
  ],

  "agent": [
    {
      "fhir_comments": [
        "  author = Harold Hippocrates  "
      ],

      "role": {
        "system": "http://hl7.org/fhir/provenance-participant-role",
        "code": "author"
      },
      "type": {
        "system": "http://hl7.org/fhir/provenance-participant-type",
        "code": "person"

      "actor": {
        "reference": "Practitioner/xcda-author"

      },
      "reference": "mailto:grahame@healthintersections.com.au",
      "display": "Grahame Grieve"

      "userId": {
        "fhir_comments": [
          "  very often, the user won't have a known system - these aren't available \n      for security system log ons. But where you can define it, you should  "
        ],
        "system": "http://acme.com/fhir/users/sso",
        "value": "hhd"
      },
      "relatedAgent": [
        {
          "type": {
            "text": "used"
          },
          "target": "#a1"
        }
      ]

    },
    {
      "id": "a1",
      "fhir_comments": [
        "  device = software Harold used  "
      ],

      "role": {
        "system": "http://hl7.org/fhir/provenance-participant-role",
        "code": "source"

        "system": "http://hl7.org/fhir/v3/ParticipationType",
        "code": "DEV"

      },
      "actor": {
        "reference": "Device/software"
      }
    }
  ],
  "entity": [
    {
      "fhir_comments": [
        "  information extract from a CCDA referral document  "
      ],
      "role": "source",

      "type": {
        "system": "http://hl7.org/fhir/provenance-participant-type",
        "code": "document"

        "fhir_comments": [
          "  this code is extracted from the CDA source document  "
        ],
        "system": "http://loinc.org",
        "code": "57133-1",
        "display": "Referral note"

      },
      "reference": "urn:iso:std:21090",
      "display": "ISO 21090"

      "reference": "DocumentReference/90f55916-9d15-4b8f-87a9-2d7ade8670c8",
      "_reference": {
        "fhir_comments": [
          "  \n      the document is in an XDS repository. \n      as a source, we're going to give an MHD \n      reference. (easier than XDS.b call with parameters!)\n\n      Note that though this is a URI, so that you can reference\n      outside FHIR, you can also put a standard FHIR reference \n      here as well\n     "
        ]
      },
      "display": "CDA Document in XDS repository"

    }
  ]
}

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.