Snapshot 3: Connectathon 32 Base

This is Snapshot #3 for FHIR R5, released to support Connectathon 32. For a full list of available versions, see the Directory of published versions.

Example Permission/example-saner (JSON)

Security Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

Raw JSON (canonical form + also see JSON Format Specification)

Example of permission for SANER

{
  "resourceType" : "Permission",
  "id" : "example-saner",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n      <p>\n    Read-Only access to SANER report is authorized for PurposeOfUse of Public-Health compliance, from the Organizations.\n    Access requests authorized shall be recorded.  \n    </p>\n      <p> \n    TODO: expression help. No access is granted to previous historic revisions (only current report).\n    </p>\n      <p> \n    TODO: authorize a Group/P1. \n    </p>\n    </div>"
  },
  "status" : "active",
  "asserter" : {
    "reference" : "Organization/f203"
  },
  "date" : ["2018-12-24"],
  "combining" : "deny-overrides",
  "rule" : [{
    "type" : "permit",
    "data" : [{
      "expression" : {
        "language" : "text/fhirpath",
        "expression" : "http://hl7.org/fhir/uv/saner/Measure/CDCHealthcareSupplyPathway"
      }
    }],
    "activity" : [{
      "actor" : [{
        "reference" : "Organization/f203"
      }],
      "action" : [{
        "coding" : [{
          "system" : "http://terminology.hl7.org/CodeSystem/consentaction",
          "code" : "access"
        }]
      }],
      "purpose" : [{
        "coding" : [{
          "system" : "http://terminology.hl7.org/CodeSystem/v3-ActReason",
          "code" : "HCOMPL"
        }]
      }]
    }],
    "limit" : [{
      "coding" : [{
        "system" : "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "code" : "AUDIT"
      }]
    }]
  }]
}

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.