Provider Connect Australia (PCA) FHIR Implementation Guide 2.4.0

This is release 2.4.0 of Provider Connect Australia (PCA) FHIR Implementation Guide. It is based on FHIR version 4.0.1. See the Directory of published versions.

CodeSystem-pca-provenance-activity-type

Formats: Narrative, XML, JSON, Turtle

Raw json


{
  "resourceType" : "CodeSystem",
  "id" : "pca-provenance-activity-type",
  "meta" : {
    "profile" : [
      "http://hl7.org/fhir/StructureDefinition/shareablecodesystem"
    ]
  },
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>This code system <code>http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-provenance-activity-type</code> defines the following codes:</p><table class=\"codes\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style=\"white-space:nowrap\">CREATE<a name=\"pca-provenance-activity-type-CREATE\"> </a></td><td>create</td><td>Description:Fundamental operation in an Information System (IS) that results only in the act of bringing an object into existence. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. For an HL7 Act, the state transitions per the HL7 Reference Information Model.</td></tr><tr><td style=\"white-space:nowrap\">UPDATE<a name=\"pca-provenance-activity-type-UPDATE\"> </a></td><td>revise</td><td>Definition:Fundamental operation in an Information System (IS) that results only in the revision or alteration of an object. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface.</td></tr><tr><td style=\"white-space:nowrap\">VRF<a name=\"pca-provenance-activity-type-VRF\"> </a></td><td>verifier</td><td>A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.</td></tr></table></div>"
  },
  "url" : "http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-provenance-activity-type",
  "version" : "2.4.0",
  "name" : "PcaProvenanceActivityType",
  "title" : "PCA Provenance Activity Type",
  "status" : "draft",
  "experimental" : false,
  "date" : "2023-09-15T10:45:26+10:00",
  "publisher" : "Australian Digital Health Agency",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "email",
          "value" : "[email protected]"
        }
      ]
    }
  ],
  "description" : "The PCA Provenance Activity Type code system defines the concepts that identify the types of activities performed by the PCA service that are documented in a Provenance resource.",
  "copyright" : "Copyright © 2023 Australian Digital Health Agency - All rights reserved. This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/.",
  "caseSensitive" : true,
  "compositional" : false,
  "versionNeeded" : false,
  "content" : "complete",
  "count" : 3,
  "concept" : [
    {
      "code" : "CREATE",
      "display" : "create",
      "definition" : "Description:Fundamental operation in an Information System (IS) that results only in the act of bringing an object into existence. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface. For an HL7 Act, the state transitions per the HL7 Reference Information Model."
    },
    {
      "code" : "UPDATE",
      "display" : "revise",
      "definition" : "Definition:Fundamental operation in an Information System (IS) that results only in the revision or alteration of an object. Note: The preceding definition is taken from the HL7 RBAC specification. There is no restriction on how the operation is invoked, e.g., via a user interface."
    },
    {
      "code" : "VRF",
      "display" : "verifier",
      "definition" : "A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability."
    }
  ]
}