...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
- FHIR Working Meeting
- Meeting schedule
FHIR FG weekly meeting
- Thursday, January 7th @ 10:00 US PT / 18.00 CET
- Zoom link: https://zoom.us/j/93406719136?pwd=SUozZHBQM0N5TUhYMHJqL0ZQM3l3Zz09
Attendees:
John Walker
Burak Serdar
Mukundan Parthasarathy
Topics: Summarize feedback to the larger Working Group
- OCA Core Data Types
- Will require a type mapping from FHIR
- This work effort and team has concerns with this conversions on healthcare data
- We understand that the BIT attributes will remain OCA base schema
- Projection Overlays - Extensions
- Projection overlay definition: "The projection overlay should describe the transformation of external schema / data object representations into an OCA formatted schema instance. The projection overlay would require a source and destination schemas.
General Business:
- JW
- FHIR Working Meeting
- Meeting schedule
FHIR FG weekly meeting
- Thursday, December 17th @ 08:00 US PT / 16.00 CET
- Zoom link: https://zoom.us/j/93406719136?pwd=SUozZHBQM0N5TUhYMHJqL0ZQM3l3Zz09
Attendees:
John Walker
Burak Serdar
Mukundan Parthasarathy
Topics: Summarize feedback to the larger Working Group
- Following from "Transformation of OCA Artifacts" discussion
- Feedback from presentation
- Candidate RFC's
- Removal of BIT attributes from OCA base schema
- This approach would allow OCA to leverage existing / multiple BIT based schemas
- Removal of BIT attributes from OCA base schema
- Projection Overlays - Extensions
- Projection overlay definition: "The projection overlay should describe the transformation of external schema / data object representations into an OCA formatted schema instance. The projection overlay would require a source and destination schemas.
General Business:
- JW - In the conversion of the DSWG to ISWG, it seems the working notes from 2 meetings have been 'misplaced' - we'll inquire if they can be re-inserted?
- Holiday Schedule - next meeting will be Thursday Jan 7, 2021
- FHIR Working Meeting
- Meeting schedule
FHIR FG weekly meeting
- Thursday, December 10th @ 08:00 US PT / 16.00 CET
- Zoom link: https://zoom.us/j/93406719136?pwd=SUozZHBQM0N5TUhYMHJqL0ZQM3l3Zz09
Attendees:
John Walker
Burak Serdar
Topics: Summarize feedback to the larger Working Group
- Following up from Tuesday's WG working meeting and the "Transformation of OCA Artifacts" discussion
- Feedback from presentation
- We've had no feedback other than what was shared in the meeting.
- Link to presentation:
- Candidate RFC's
- Projection Overlays
- Removal of BIT attributes from OCA base schema
- This approach would allow OCA to leverage existing / multiple BIT based schemas
- Overlays - Extensions
- Projection overlay definition: "The projection overlay should describe the transformation of external schema / data object representations into an OCA formatted schema instance. The projection overlay would require a source and destination schemas.
- (Please see Google doc - WIP)
- Projection overlay definition: "The projection overlay should describe the transformation of external schema / data object representations into an OCA formatted schema instance. The projection overlay would require a source and destination schemas.
- Feedback from presentation
General Business:
- TBD
- FHIR Working Meeting
- Meeting schedule
FHIR FG weekly meeting
- Thursday, November 19th @ 08:00 US PT / 16.00 CET
- Zoom link: https://zoom.us/j/93406719136?pwd=SUozZHBQM0N5TUhYMHJqL0ZQM3l3Zz09
Attendees:
John Walker
Mukundan Parthasarathy
Burak Serdar
Albert (SSI/Blockchain startup, Bordeaux, France)
Topics: Summarize feedback to the larger Working Group
- Following up from the last working meeting on the topic of taking a complex, nested json object and render that into OCA Base + Overlays
- Simple demonstration of an example FHIR resources expressed as JSON-LD
- ex: Immunization resource instances
- Use these instances to demonstrate the potential variations in valid instance within the same bundle
- Ex: What is the syntax for selecting Immunization/vaccineCode/coding/code?
- How does this work with array fields: Immunization/performer is an array of objects, how do you select all of them? How do you select a particular one?
- Use this example to explain the use of a "projection overlay" for instance mapping
- ex: Immunization resource instances
- Overlays - Extensions
- Blinding Identity Overlay - Assume that the BIT attribute assignment in the base schema is a union of all potentially attributes needing 'blinding'
- Demonstrate the use of 'conformance-type' and 'conformance spec' as the specification mechanism to identify blinded attributes → drive the related RFC discussion
- Agreement on handling profiles/extensions via conformance-type and conformance-spec headers v/s separate overlay for handling conformance to profiles such as us-core etc.
- [Burak] Overlay selector idea based on use cases (to be explored: tags, fhirpath or some such spec to identify the use cases/context for use of overlays)
- Demonstrate the use of the Masking Overlay to apply blinding to an FHIR OCA instance
- Projection overlay for flattening. Sub-setting overlay may not meet all the needs. Barak shared ideas around a "mapping" format that can be used in the definition of the Projection overlay, so as to simplify the "flattening" problem, for the purposes of data capture/display in OCA "forms".
- Potential uses of the Subset Overlay
- Discussion
- Simple demonstration of an example FHIR resources expressed as JSON-LD
General Business:
- JW - Propose this standard meeting frequency is changed to bi-weekly frequency occurring at 8:00am PT on Thursdays
- FHIR FG Working Meeting
- Meeting schedule
FHIR FG weekly meeting
- Thursday, November 12th @ 15:00 US PT / 00.00 CET
- Zoom link: https://zoom.us/j/93406719136?pwd=SUozZHBQM0N5TUhYMHJqL0ZQM3l3Zz09
Attendees:
John Walker
Mukundan Parthasarathy
...
- Following up from the last working meeting on the topic of taking a complex, nested json object and render that into OCA Base + Overlays
- Source FHIR EHR → Base
- Burak - "how do we bridge schema to data?" Solution could be a capture schema to limit the fields, and use a projection overlay to map to the OCA form.
- New
- Overlays - Extensions / updates
- Blinding Identity Overlay - Assume that the BIT attribute assignment in the base schema is a union of all potentially attributes needing 'blinding' - ? from 10/29 meeting notes - the suggestion is to use 'conformance-type' and 'conformance spec' as the specification mechanism to blind specific attributes ? Yes, working group proposal is to create or update the existing RFC's to propose the addition of 'conformance-type' and 'conformance-spec' as attributes in both the OCA SB and OCA Overlay specification.
- How is this implemented? Application (FHIR) bundle specific contexts for blinding attributes
- Need a better way of selecting fields in overlay specifications, especially for nested data structures like JSON/XML
- Ex: What is the syntax for selecting Immunization/vaccineCode/coding/code?
- How does this work with array fields: Immunization/performer is an array of objects, how do you select all of them? How do you select a particular one?
- Ex: What is the syntax for selecting Immunization/vaccineCode/coding/code?
- Blinding Identity Overlay - Assume that the BIT attribute assignment in the base schema is a union of all potentially attributes needing 'blinding' - ? from 10/29 meeting notes - the suggestion is to use 'conformance-type' and 'conformance spec' as the specification mechanism to blind specific attributes ? Yes, working group proposal is to create or update the existing RFC's to propose the addition of 'conformance-type' and 'conformance-spec' as attributes in both the OCA SB and OCA Overlay specification.
- Source FHIR EHR → Base
General Business:
- JW - standard meeting time changed to 8:00am PT every Thursday
- FHIR FG Working Meeting
- Meeting schedule
FHIR FG weekly meeting
- Thursday, October 29th @ 07:00 US PT / 16.00 CET
- Zoom link: https://zoom.us/j/93406719136?pwd=SUozZHBQM0N5TUhYMHJqL0ZQM3l3Zz09
Attendees:
John Walker
Mukundan Parthasarathy
...
- Discussion - Explore evolving how a "base schema" structure used
General Business:
- JW - change in the meeting time to 8:00am PT every Thursday
...
- FHIR FG Working Meeting
- Meeting schedule
FHIR FG weekly meeting
- Thursday, October 15th @ 07:00 US PT / 16.00 CET
- Zoom link: https://zoom.us/j/93406719136?pwd=SUozZHBQM0N5TUhYMHJqL0ZQM3l3Zz09
Attendees:
John Walker
Mukundan Parthasarathy
...
- Base FHIR Conversion Updates - Overview of current work
- Review of FG Use Case 1: FHIR resource bundle export of a specific resource set targeted for consumption by a non-FHIR supported provider.
- Limited scope to begin
- Review of FG Use Case 1: FHIR resource bundle export of a specific resource set targeted for consumption by a non-FHIR supported provider.
- General discussion on OCA Implementation Applicability
- Adrian's explanation of HEofOne
- General comments on the limitations of the current FHIR based consent mechanism.
- Discussion regarding the overly complex consent / contract resource alignment.
General Business:
- JW - proposal to change the meeting time to 8:00am PT every Thursday
9/10/2020 - FHIR FG Working Meeting
Attendees:
John Walker
Mukundan Parthasarathy
...
- Use Case 1: Remotely Accessible Patient EHR - patient expressly requests creation of a FHIR based EHR representation to be used by different Health Care providers in different (same country) locale. (This use case can evolve to support crossing national boundaries thus adding complexity)
- Feedback:
- JW - Create a use case document and process template to record the use case.
- Feedback:
- ISO Context
- Will reach out to Mark Lizar for content
General Business:
- JW - will publish meeting time and link on the FHIR FG confluence page
9/3/2020 - Kick Off FG Working Meeting
Attendees:
John Walker
Mukundan Parthasarathy
...
- SM - create narrowly focused, end user centric demos to demonstrate "user" value
General Business:
- Weekly meeting start time will be moved to 7:00am PT / standing meetings planned for every Thursday.