HL7 FHIR Security 2018-09-04
Jump to navigation Jump to search
Revision as of 16:15, 4 September 2018 by JohnMoehrke (Created page with "==Call Logistics== Weekly: '''Tuesday at 02:00 pm EST''' Web conference desktop and VOIP https://www.freeconferencecall.com/join/security36 Online Meeting ID: security36 ...")
Weekly: Tuesday at 02:00 pm EST
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
|Member Name||Member Name||Member Name|
|x||John Moehrke Security Co-Chair||x||Kathleen Connor Security Co-Chair||.||Alexander Mense Security Co-chair|
|x||Suzanne Gonzales-Webb CBCC Co-Chair||.||Johnathan Coleman CBCC co-chair||.||Chris Shawn Security co-chair|
|x||Jim Kretz||.||Kenneth Salyards||.||Nathan Botts Mobile co-chair|
|.||Diana Proud-Madruga||x||Joe Lamy AEGIS||.||Beth Pumo|
|.||Irina Connelly||.||Matt Blackman Sequoia||.||Mark Underwood NIST|
|.||Peter Bachman||.||Grahame Greve FHIR Program Director||.||Kevin Shekleton (Cerner, CDS Hooks)|
|.||Luis Maas||.||Julie Maas||.||Francisco Jauregui|
|.||Gary Dickinson||.||Dave Silver||.||Foo Bar|
- approval of agenda
- approval of HL7 FHIR Security 2018-08-28 Minutes
- Process for "Security and Privacy Considerations" section
- Plan for maturing security (and privacy) parts of FHIR -- FMM
- All security open http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677&tracker_query_id=4967
- New business
- John - forward safety checklist updates with explanation to FHIR-I
- John - propose next steps on "Security Considerations" on each FHIR page
- John - bring proposal to Grahame to see how the FHIR build tools can aid us
Security Considerations on each page
- General sensitivity:
- All resources can contain sensitive information, these groups are only general expectations based on the Resource intended use-case
- Public/Infrastructure, --- Should be Public and not sensitive themselves, but care as inappropriate use might put sensitive information within
- Bundle, Linage, MessageHeader, OperationOutcome, Parameters, Subscription, CapabilityStatement, StructureDefinition, ImplementationGuide, SearchParameters, MessageDefinition, OperationDefinition, CompartmentDefinition, StrucureMap, GraphDefinition, ExampleScenario, CodeSystem, ValueSet, ConceptMap, NamingSystem, TermininologyCapability, Library, Questioniare, ActivityDefinition, DeviceDefinition, EntryDefinition, EventDefinition, ObservationDefinition, PlanDefinition, SpecimenDefinition, TestScript, TestReport
- Business-Sensitive, --- Mostly Public and not sensitive, but care as they may contain business sensitive
- Organization, OrganizationAlliliation, HealthcareServices, Endpoint, Location, Substance, BiologicallyDerivedProduct, Device, DeviceMetric, Task, PractitionerRole, Schedule, Slot, ProcessRequest, ProcessResponse, Measure, MeasureReport
- all of the Financial ????
- all of the Medication Definition ???
- Provider-Sensitive, --- Provider identified data, may be appropriate to release for specific use-cases, but does expose the provider individual
- Appointment, AppointmentResponse, Practitioner, PractitionerRole, Person, CareTeam
- all Patient-Sensitive
- all of the Financial
- Patient, RelatedPerson, Person, Encounter, EpisodeOfCare, Flag
- all of the Clinical
- all of the Financial
- Unknowable -- Could contain anything, thus might be public or might be highly sensitive
- Binary, List, Group, QuestionaireResponse
- To focus on FHIR as a scoping mechanism. That is to say that this effort could be applied everywhere, but we need to start somewhere. There has been some interest for this kind of review in FHIR.
- Person resource http://build.fhir.org/person.html#security
- Much like IETF has with W3C PING?
- W3C PING https://w3c.github.io/privacy-considerations/
- W3C specification for writing Privacy Considerations http://yrlesru.github.io/SPA/
- W3C Self-Review Questionnaire: Security and Privacy https://www.w3.org/TR/security-privacy-questionnaire/
- IETF guidance on writing the Security Considerations section https://tools.ietf.org/html/rfc3552
- IETF guidance on writing a protocol module -- a description of your standard so that an analysis can be made https://tools.ietf.org/html/rfc4101
- Could try to apply W3C process without customization to see how well it applies?
- W3C Self-Review Questionnaire: Security and Privacy -- GITHUB active version https://w3ctag.github.io/security-questionnaire/
- Note not all FHIR resources are sensitive, some are intended to be publicly exposed.
- stream for Security and Privacy discussions. Specification development, and Implementation.
- stream for Patient Empowerment. Discussions about empowering patients. Focus on deployment and advocacy.
- Proposed FHIR Connectathon track for Cologne -- GDPR
- Blockchain FHIR Connectathon
- Grahame is trying to find a community wanting to 'play' with blockchain. He is willing to standup the infrastructure.
- See blockchain zulip stream https://chat.fhir.org/#narrow/stream/blockchain
- Certificate Management
- Improvement beyond SMART scopes
- Patient Directed backend communication
- Oauth App Registration
Current Open issues in gForge
- 9167 AuditEvent+needs+to+make+more+obvious+how+to+record+a+break-glass+event (John Moehrke) Considered for Future Use
- 10343 Three+additional+Signature.type+codes (Kathleen Connor) Considered for Future Use
- 11071 Improve+security+label+guidance+-+2016-09+core+%2390 (Kathleen Connor) None
- 12660 HCS+use+clarification (John Moehrke) None
- 17192 Verification+of+given+resource+without+changing+the+content (Thomas Johansen) None
- 17299 enhance+current+disclosure+AuditEvent+so+that+it+explains+what+is+being+recorded+and+why (John Moehrke) None
- 17300 Break-Glass+description+needs+clarifications (John Moehrke) None
- 14678 Implementation+guide+for+signatures+-+2018-Jan+Core+%231 (Brian Pech) Not Persuasive
- John chaired