Release 5 R6 Ballot (2nd Draft)

This page is part of the FHIR Specification (v5.0.0: R5 - STU v6.0.0-ballot2: Release 6 Ballot (2nd Draft) (see Ballot Notes ). This is the The current published version in it's permanent home (it will always be available at this URL). is 5.0.0 . For a full list of available versions, see the Directory of published versions

Example AuditEvent/example-consent-permit-authz (Narrative)

Security Work Group Maturity Level : N/A Standards Status : Informative Compartments : Device , Patient , Practitioner

This is the narrative for the resource. See also the XML , JSON or Turtle format. This example conforms to the profile AuditEvent .

Generated Narrative: AuditEvent example-consent-permit-authz

Resource AuditEvent "example-consent-permit-authz"

type : Security Alert

code subtype : Query ( DICOM #110112)

action : E

recorded : 9 Sept 2021, 7:51:59 am 2021-09-08T21:51:59.932Z

Outcomes

- Code Detail
* AuditEventOutcome 0: Success (Details: http://terminology.hl7.org/CodeSystem/audit-event-outcome code 0 = 'Success', stated as 'Success') CONSENT_PERMIT ()

patient : Patient/example Jim male, DoB: 1974-12-25 ( Medical record number (use: usual, period: 2001-05-06 --> (ongoing))) "Peter CHALMERS"

Agents

- Type Who Requestor Authorization
* Destination Role ID ( DICOM #110152) Identifier: https://github.com/synthetichealth/synthea /Org1 true treatment ( ActReason #TREAT)

Sources

- Observer Type
* : LEAP Consent Decision Service Application Server ( Audit Event Source Type #4)

Entities

- What Role
* Consent/consent-example-basic Consent: status = active; category = Patient Consent; date = 2018-12-28; regulatoryBasis = information access; decision = deny Domain Resource ( AuditEventEntityRole #4)

 

 

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.