This wiki has undergone a migration to Confluence found Here

HL7 FHIR Security 2018-02-06

From HL7Wiki
Jump to navigation Jump to search

Call Logistics

Weekly: Tuesday at 05:00 EST (2 PM PST)

Web conference desktop and VOIP https://www.freeconferencecall.com/join/security36 
Online Meeting ID: security36
Phone: +1 515-604-9567, Participant Code: 880898
 Please be aware that teleconference meetings are recorded to assist with creating the meeting minutes 

Back to HL7 FHIR security topics

Attendees

Member Name Member Name Member Name
x John Moehrke Security Co-Chair x Kathleen Connor Security Co-Chair . Alexander Mense Security Co-chair
. Suzanne Gonzales-Webb CBCC Co-Chair . Johnathan Coleman CBCC Co-Chair . Mike Davis
. Reed Gelzer RM-ES Lead . Glen Marshal x Joe Lamy AEGIS
. Diana Proud-Madruga . Rob Horn . Beth Pumo
. Irina Connelly . Mario Hyland AEGIS . Mark Underwood NIST

Agenda


Minutes

  • John chaired
  • did not review previous minutes
  • Reviewed current block vote candidates
    • Kathleen wants to add to 14028
    • Joe provided some fixes to existing wording proposal
  • Reviewed those not in block vote
  • Worked on mapping Provenance with Event Pattern
    • Event pattern requires a status element. Provenance is a statement, not a resource that will go through a lifecycle
    • Event pattern requires a subject element. Provenance is used for all FHIR Resources, therefore there is no dedicated subject element. Provenance is discovered from the target it points at, not from the subjects.
    • It does seem that Provenance.reason should get renamed to Provenance.purpose so that it is more clear, and so that it doesn't conflict with Event.reasonCode concept.
    • It does seem that activity should get renamed to reasonCode as it is the activity that caused the create/update/delete that is preserved in Provenance. It is not clear, so need more thought on this one.
    • Should rename agent to performer. This would be better understood in context of the Event pattern, and also by the records and security domains.
  • AuditEvent
    • Similar observations to Provenance
  • Action: John to bring this up with Lloyd