Skip to end of metadata
Go to start of metadata

Chair:  John Moehrke

Scribe: John Moehrke  


Mondays at 12:00 pm Eastern Time - http://join.freeconferencecall.com/security36

NOTE: This attendance applies if you are present at the related meeting/call, regardless if you have signed a different attendance for your WG. 

Attendees


Minutes Approved as Presented 2020-01-06 FHIR-Security Meeting Agenda, and 2020-02-24 FHIR-Security Meeting Agenda

This is to approve minutes via general consent. "You have received the minutes. Are there any corrections to the minutes? (pause) Hearing none, if there are no objections, the minutes are approved as printed."


Agenda Topics

Agenda Outline

Agenda Item

Meeting Minutes from Discussion

Decision Link(if not child)
Management Minutes Approvalapproved by general consent
newsNo meeting next week due to HIMSS protect yourself at HIMSS, don't touch face, wash hands often.

Permission Resource

http://build.fhir.org/permission is prototyped

robust discussion on how this might be the basis for more refined redaction such as a permission that allowed a given role to have access to the Patient resource but not the Patient.identifier that holds a given national ID value

This might be by having a Permission.useLimitations that identifies these fine-grain restrictions

Alternative proposed elsewhere is to add a security tag to all elements in all resources; which seems to be more burdensome

John presented 

Discussion

  • Luis - worried that it is intended to hold rules that would be internal only, thus should focus on when rules are Interop needed
  • Kathleen - would be good to harmonize with Contract too
  • Luis - might be a good backbone structure used by Consent and Contract
    • Might be needed beyond those two, so it is starting as a Resource
  • Luis - should this be called Grant rather than Permission?


FHIR IG Proposal for gov work (confluence and build shown in github readme)

https://github.com/HL7/us-security-label-regs 

Kathleen has updated text in a word document

John will focus on previous action items to separate out and correct valuesets



FHIR IG for DS4P 

https://github.com/HL7/fhir-security-label-ds4p

Confluence: FHIR DS4P IG

GitHub exists

Need IG template to get this started

Kathleen has initial text in word document


In Process




waiting on dicom

FHIR-24907 – Lifecycle event valueset should include HL7 lifecycle event vocabulary (ISO 10781) – bring in HL7 lifecycle event vocabularywaiting on iso

FHIR-24676 - PurposeOfUse vocabulary from ISO 14265 – bring in ISO vocabularywaiting on iso

FHIR-23712 - Getting issue details... STATUS  waiting on ISO

waiting on iso

FHIR-11071 - Getting issue details... STATUS  DS4P and CUI will be creating IG. This exercise will result in update of the FHIR core with informed instructions

moved to DS4P
Open Items

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh







































FHIR BlockBlock vote preparation


none





FMMDefined plan to mature

Connectathon Update on Security at FHIR connectathon

SMARTdiscussion of next generation of SMART https://chat.fhir.org/#narrow/stream/179170-smart/topic/SMART.20scopes.20v2no activity. Is this existing STU potentially expiring this year?




Management Next agenda

New Business



 Adjournment
40 minutes

Supporting Documents

Outline Reference

Supporting Document

Minute Approval

 


Tasks