Chair: @David Pyke
Scribe: @Suzanne Gonzales-Webb
Johnathan Coleman Co-Chair
Suzanne Gonzales-Webb Co-Chair
|VA (Book Zurman)|
David Pyke Co-Chair
|Ready Computing||@Jim Kretz Co-Chair||SAMHSA|
John Davis aka Mike Davis
|VA||x||Kathleen Connor||VA (Book Zurman)|
|Georgia Tech||x||Chris Shawn||VA|
|Iris Health Solutions|
|Altarum||@Francisco Jauregui||VA (Electrosoft)|
|x||Greg White||SRS||x||@Pele Yu email@example.com||Children's Hospital|
|@Amber Patel||SRS||x||SSA (Aegis)|
|Beth Pumo||Kaiser||x||@Laura Bright firstname.lastname@example.org|
@Forrest White email@example.com
|x||Jamie Parker||Carradora||x||@Matt Lord firstname.lastname@example.org||MDIX Inc|
|x||@Hanna Galvin email@example.com|
Meeting Minutes from Discussion
|Decision Link(if not child)|
VOTE: (motion) :
Abstain: none / Opposed: none / Approve: 18
eLTSS bi-Monthly report out
Please contact Johnathan Coleman or Becky Angeles for more information and meeting link!
information sent to group list with meeting information (contact Becky Angeles to be added)
To join the meeting on 6/13:
URL: https://chiwebex1seats50.my.webex.com/chiwebex1seats50.my/j.php?MTID=m10965c2bbe754e5769f0e44b77c52087 <https://healthit.us19.list-manage.com/track/click?u=8d40fc226045608875374f0f1&id=76be3007da&e=177d086d0e>
Dial-In: + 510-338-9438; Access code: 621 054 615
Meeting password (if needed): meet
|NPRM Comments (overview) - Kathleen||HL7 Response Letter ONC 21st Century Cures Act v05.27.19 presented by Kathleen - DISCUSSION|
from 5/28 meeting ---
still refining the comments, they have not gone to the Board as of yet; extension of comment dates to June 3
Link to latest DRAFT: https://confluence.hl7.org/display/SEC/TEFCA+2+Security+CBCP+Comments
|Discussion: use-case of registering a Privacy Consent that authorizes a proxy - Feliano "Pele" Yu, David Pyke, John Moehrke|
Proxy - we are currently try to advance xx; into the care plan as appropriate; most of what you are describing appears to fall under policy–policy under individuals/institutions
i.e.. Patient A - decided to not permit access to certain data elements as patients move in/out of certain facilities - putting a child at risk / for each data element which are deemed sensitive by the provider or individual can they put some sort of flag (i.e. security labeling) on the information
there are two different models
e-mail string below
5/15 - (JMoehrke) added Dave Pyke (to e-mail string), he is the co-chair of the committee that owns the Consent resource in FHIR, and is the one that leads that effort. His committee meets Tuesday mornings.
I would say that the Consent Resource alone is not enough. You certainly can provide implementation guidance on how the FHIR Consent resource would be used in your environment with your policies. But even this is not sufficient to address all of the issues contained in your policies. You would also need to identify other functionality that would be needed to assure the rules recorded in a Consent are adhered to. You would also need to require that AuditEvent be recorded so as to track uses of data for those patients, so that reports could be supplied with various use and disclosure actions. There would also need to be controls around verifying that the system is working as defined.
What you are after is a layer of specification that more specific to your policy and setting than would be written by HL7. There is a need for this kind of specification, but it is not possible to write these kinds of implementation guides without understanding the setting and the policies. Thus this kind of a specification is often done on a per-project basis.
Pele Yu: FHIR-enabled “proxy” access to patient portals for pediatric patients/specific FHIR that could be very useful pediatrics, and this is related to “proxy” access to patient portals.
We are exploring this opportunity in the peds community and I am attaching our ONC comment/response to define the problem space. As you can see, the use cases below “proxy”, “forbidding access”, among others are part of the problem space.
JMoehrke: For the use-case of registering a Privacy Consent that authorizes a proxy. Use-cases for any authorized designate. Also for emancipated minor elevation of rights. Also for forbidding access to otherwise recognized (abusive spouse).. .. that is in the Consent resource...
I am not sure what else is intended by proxy. I can imagine so many things.
|eLTSS Use Case - Craig (15-20 min)|
Display of Forrest screen;
(Altarum) working on an eLTSS use case for exchanging data between a beneficiary and a care coordinator.
Review use case/s to make sure it matches what the eLTSS team was envisioning. Altarum is interested in this use case as being part of the Connectathon track in Atlanta. Note: still working on the documentation, but will provide to the CBCP listserv ahead of time for folks to take a look at.
|eLTSS FHIR IG Project - Becky, Johnathan|
Final negative withdrawn
reconciliation complete, no outstanding comments
changes approved during reconciliation are in process - or already implemented. there will be some reivew of the updates to confirm the updated mappings are in the right place
Question: the updated IG is on the fhir.build.org (wills stay there until the publication is sent/approved)
|CBCP FHIR Consent CPs-DavidP||for 6/11 - if time permits|
|Provenance DAM - Mike Davis||for 6/11 - if time permits|
|DS4P FHIR IG|
updates, if time permits
PSS Approved 6/4/2019: FHIR Data Segmentation for Privacy (DS4P) Implementation Guide PSS
|September 2019 WGM||if time permits|
|Additional Agenda Items|
|Adjournment||Meeting adjourned at Arizona Time: (Johnathan) meeting adjourned at 1001 Arizona Time||Temporary Meeting Recording: https://fccdl.in/fKN5l03Pcs|