Solution Architecture work stream

RE: On the question of Complex vs. Simple FHIR extensions

FYI: The question is posted to chat.fhir.org.

Is anyone opposed to more governance discussion on Friday 10/4 if nothing else is added to the agenda?

Have we determined what specific comments will be presented to the Ministry at the FHIR North conference on 10/16? Should we spend some of our time gathering our thoughts to be able to better articulate our case?

I'm regulatory and policy-driven and would like to assist this effort from that angle.

I have enjoyed reading the discussions on this thread. Thank you all for your continued effort and tireless work.

On the question of COmplex vs. Simple FHIR extensions, two comments:
1. This is exactly the sort of question that's good to raise on chat.fhir.org. (Both because it'd get an answer faster there and because it would be useful to the broader community.)
2. Best practice is the same as it is for resources. Don't introduce a grouper unless the grouper is don't something useful - i.e. there's a need for a collection of items to repeat as a group or a collection is optional as a group. As much as possible, we avoid introducing layers. Plus, grouping can sometimes make things harder to find and/or re-use.

Open call for any agenda items the community would like to raise or discuss.

There are currently no planned agenda items for Friday, October 4th, 2019.

If no agenda items are raised by 1PM EDT, the call may be cancelled.

2019-09-20 FHIR Solution Architecture Work Stream Minutes:

Attendees:

• Ken Sinn
• Igor Sirkovich
• Fang Cao
• Rita Pyle
• Bryan Dearlove
• Janice Spence
• Radhika Verma
• Randy Nonay
• Shamil Nizamov
• Thomas Zhou
• Harsh Sharma

Minutes:

Ken Sinn was nominated for Co-Chair, motion passed with nobody abstaining or against.

Agenda to discuss two forum topics raised by Shamil:
1. FHIR FAST - CA-Core into the HIAL
2. Complex vs Simple FHIR Extensions

FHIR FAST (FHIR At Scale Taskforce)
- ONC initiative to address scalability
- recognition that current ecosystem is very point-to-point
- want to create a single consolidated API endpoint and integration layer, similar to HIAL
- not clear if FAST is an architecture design pattern, an architecture profile, or an actual product; Shamil to investigate and provide future updates
- suggestion for eHealth Ontario representative to walk through the Ontario EHR solution

Complex vs Simple FHIR Extensions
- question raised on best practices for extension design, whether to group multiple related extension elements together
- choice of complex vs simple may impact development complexity, and having to iterate through FHIR extensions; Igor suggested using pre-built FHIR libraries, which should handle extensions, rather than trying to build from scratch
- Shamil to provide a better example to illustrate this issue
- Igor to solicit chat.fhir.org/zulip for best practices around complex vs simple extensions

Action Items:
- Ken S. to provide Randy Nonay with presentation/recording of eHealth Ontario OIDs/URIs webinar
- Ken S. to provide Thomas Zhou access to the eReferral iGuide on Simplifier

FYI: US has started ONC lead FAST (FHIR at Scale) initiative. I attended the info webinar last week[1] and it resembled me our HAIL verbatim.
Any ideas to inject FHIR (CA Core) into HIAL?

[1] - oncprojectracking.healthit.gov/wiki/display/TechLabSC/FAST+101+Informational+Webinar