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 AuditEvent/example-disclosure (Narrative)

Security Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: 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

Resource AuditEvent "example-disclosure"

category: Export (DICOM#110106)

code: HIPAA disclosure ([not stated]#Disclosure)

action: R

severity: notice

recorded: 22 Sept 2013, 10:08:00 am

Outcomes

-CodeDetail
*Success (Details: http://terminology.hl7.org/CodeSystem/audit-event-outcome code success = 'Success', stated as 'Success')Successful Disclosure ()

authorization: healthcare marketing (ActReason#HMARKT)

patient: Patient/example "Peter CHALMERS"

agent

type: Source Role ID (DICOM#110153)

who: : That guy everyone wishes would be caught

requestor: true

location: Location/1 "South Wing, second floor"

policy: http://consent.com/yes

network: custodian.net

agent

type: Destination Role ID (DICOM#110152)

who: Practitioner/example: Where "Adam CAREFUL"

requestor: false

network: marketing.land

authorization: healthcare marketing (ActReason#HMARKT)

Sources

-ObserverType
*: Watchers Accounting of Disclosures ApplicationApplication Server (Audit Event Source Type#4)

Entities

-WhatRoleSecurityLabel
*Patient/example/_history/1: data about Everthing important "Peter CHALMERS"Domain Resource (AuditEventEntityRole#4)very restricted (Confidentiality#V), sexually transmitted disease information sensitivity (ActCode#STD), delete after use (ActCode#DELAU)

 

 

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.