Privacy on FHIR
Meeting Agenda and Minutes
Agenda & Meeting Minutes
Purpose of Meeting: Introductions and Review of Use Cases
Date & Time: Tuesday Jan 13, 2015 4-5PM Eastern
Location: United States: +1 (626) 521-0016 United States (toll-free): 1 866
899 4679
Access Code: 782820893
Meeting. https://global.gotomeeting.com/join/782820893
Audio PIN: Shown after joining the meeting
Meeting Password: FHIR
Meeting ID: 782-820-893
POF WIKI:
http://wiki.siframework.org/Privacy+on+FHIR
Facilitator: Mike Davis
Meeting Support:
Attendees: O = Onsite Attendee; P = Phone Attendee; X = Not Attending
o Mike Davis (VA)
Athy Conigliaro
o Mike Dufel (Jericho)
Adrian Gropper (PPR)
Brynn Mow (Jericho)
Mohammad Jafari (VA)
Dave Hill (MITRE)
Nagesh Bashyam (Dragon) (ONC)
David Staggs (Jericho)
Nate Gould (DoD)
o Orlando Concha (Jericho)
Debbie Bucci (ONC)
o Raymond Kimble (ONC)
Duane DeCouteau (VA)
Gerry Gebel (Axiomatics)
Ross Freeman (Jericho)
John Pitale (VA)
Salim K. Semy (MITRE)
Johnathan Coleman (ONC)
Suzanne Gonzales-Webb (VA)
Josh Mandel (MIT)
Taylor Gill (Jericho)
Judy Fincher (VA)
Terry Luedtke (VA)
o
o
Justin Richer (MITRE/MIT)
o Thomas Hardjono (MIT)
o
Kathleen Connor (VA)
Ken Salyard (SAMHSA)
o Tim McGrail (VA)
o Tony Mallia (VA)
William Israel (Jericho)
o David Bergman
o
Katherine Wetherby (SAMHSA)
Vijay Subramanium
Agenda
Page 1 of 5
Privacy on FHIR
Meeting Agenda
ID Topic
1 Minutes, Agenda
Presenter
Kathleen, Mike
5 min
Schedule of meetings
2
Use Cases for Apps on FHIR Discussion
3
Developer’s Update
Mike
4
5
Project Deliverables
HIMSS Deliverables
1. “Wow” powered use cases meant to capture
imagination and win hearts and mind [aka “Elevator
Pitch”]
All
2. Storyboards intended to convey business
requirements and standards landscape to developers
3. Architecture
a) Choreographies and data element exchanged
b) Diagram showing subsystems and connections
between them
c) Flow diagram showing activities and message
movement between subsystems
d) Elements passed in the Tokens or request headers
relevant to access control
4. Reference Model (Open source executable code
to serve as model for developers, models,
requirements and profile)
1. “Wow” Power
 PoF Overview Presentation and HIMSS Slide
(1 per booth)
 Kathleen Use cases
2. Storyboards
 TBD
3. Architecture
a) Dragons Diagrams
b) Mohammad Diagrams
c) Mohammad Sequence Diagrams
d) Project Brief
4. Reference Models
 VA provided SLS/PPS, Test Models.
 SAMHSA Consent2Share open CDMS
Key Discussion Notes
ID Topic
1
2
Agenda
Page 2 of 5
Privacy on FHIR
Project Deliverables
3
4
Action Items
ID
Action Items
1
Assigned to
3
Due Date
How do we constrain the
scope of the use cases? We
have seven months to
complete and test Demo.
What resources are available
and what can be provided by
each of us?
Post materials to S&I PoF page
http://wiki.siframework.org/Pr
ivacy+on+FHIR
Status
Comments
0926
Added
Standards
6/2014
All
2
Assign
Date
Mike
9/2014
0912
KC
0908
0819
COMPLETE
Three
identified.
0613 Need
to know
how many
separate
items.
For Review
0923
Complete
Possible multiple
booths or POD.
1. Patient App
scenario
2. Consent
Directives
3. HIE
4. Standards on
FHIR
0829 Bill of Lading in
today’s presentation
0923 Documents
starting to be
uploaded.
0913 Dragon assisted
Mike with uploading
to the ONC PoF Wiki
4
Update the HoF diagram to
include a single trusted AS for
the Happy Path.
Tony and
Mohammad
9/22
9/26
0926
Complete
Accepted by Group
Agenda
Page 3 of 5
Privacy on FHIR
Next Meeting
TBD
Time:
Location:
Dial-In Line:
January 13 Minutes
Discussed the assignment of components per Adrian’s table and HoF Participants Information Sharing
Dragon walked through the transactions to assign developers.
Discussion on whether Alice can have one or more UMA AS.
Dragon will continue working out the assignments and send out next week.
Dragon captured the following notes from the discussion, which others will verify and KC will incorporate into the
Storyboard:
Step 1: 42 CFR (Duane), HIE (Dragon)
a.
Alice authors her consent using the Consent UI (Duane)
b.
42 CFR will check CDMS ( Duane ) protected by UMA AS (???) prior to pushing information to the HIE.
c.
42 CFR ACS (PPS, SLS) - ( Duane) will be used to label the data prior to release.
d.
Alice introduces her HIE resources to the UMA-AS
e.
ONC resources will be protected UMA AS – MIT (Justin)
f.
ONC has to expose end points for each of the resources to be created/updated by 42 CFR.
Step 2: 42 CFR (Duane), HIE (Dragon)
g.
42 CFR (Duane) expose endpoints for resources to be read. Resources protected by UMA AS (Justin)
h.
42 CFR checks CDMS (Duane), and ACS (Duane) labels data prior to release
i.
HIE (Dragon) pulls data from end points and updates local copy.
Step 3: 42 CFR (Duane), MHV (Duane)
a.
Alice authors her consent using the Consent UI (Duane)
b.
42 CFR will check CDMS ( Duane ) protected by UMA AS (???) prior to pushing information to the MHV.
c.
42 CFR ACS (PPS, SLS) - ( Duane) will be used to label the data prior to release.
d.
Alice introduces her MHV resources to the UMA-AS
Agenda
Page 4 of 5
Privacy on FHIR
e.
MHV resources will be protected UMA AS – MIT (Justin)
f.
MHV has to expose end points for each of the resources to be created/updated by 42 CFR.
Agenda
Page 5 of 5