Stream: cds hooks
Topic: Argonaut CDS Hooks
Brett Marquard (May 16 2017 at 23:56):
Howdy,
Just an FYI the Argonaut CDS Hooks project will meet this Thursday, May 18th from 3-4PM ET.
Call details:
Dial in: 866-951-1151 Code: 5093906
Webinar: https://attendee.gotowebinar.com/register/5333721393020156418
Brett Marquard (May 18 2017 at 19:45):
Thanks for a great call, presentation from today
Kalyani Yerra (Jun 13 2017 at 17:25):
As part of the CDS Hooks Argonaut, are we supporting both FHIR STU2 and STU3?
Isaac Vetter (Jun 13 2017 at 17:26):
Hey @Kalyani Yerra , I think that all (or at least most) of the CDS Hooks platforms (EHRs) still only support DSTU2.
Chuck Feltner (Jun 13 2017 at 20:15):
Our T-System EHR server supports STU3.
Kevin Shekleton (Jul 14 2017 at 03:38):
This is going to become a troublesome issue...both here in CDS Hooks and with SMART. For instance, I know of a major EHR vendor that is just now beginning to support FHIR and they are going with STU3. However, many other major EHR vendors who were much earlier to FHIR are on DSTU2 still. Officially, the Argonaut Project is still using DSTU2.
Kevin Shekleton (Jul 14 2017 at 03:40):
This is something that needs more discussion in the FHIR community.
Grahame Grieve (Jul 25 2017 at 06:50):
how to drive that discussion?
Grahame Grieve (Jul 25 2017 at 06:50):
the problem is that everyone already invested in DSTU2 will vote for that, and everyone else will vote or R3
Grahame Grieve (Jul 25 2017 at 06:51):
I had hoped that we'd get more resources on the normative track for R4, to ease this problem, but it doesn't look like it's going to go very quickly
Kevin Shekleton (Jul 25 2017 at 19:10):
@Grahame Grieve - I think we should have an open discussion about this at the WGM this Sept. There isn't an answer for this.
Kevin Shekleton (Jul 25 2017 at 19:11):
This likely should be classified as a high-class problem for FHIR -- though it is still relatively new (as compared to other standards), it's adoption is high
Grahame Grieve (Jul 25 2017 at 21:11):
agree. I'll try and drive it there. Though it's really an argonaut discussion not an HL7 discussion - different sub-communities have different answers because they are at different points in their life cycles
Kevin Shekleton (Jul 25 2017 at 21:51):
While I agree all Argonaut members would be large stakeholders in this discussion, I think it's really a discussion by anyone who:
1. Has many companies/developers coding against their FHIR implementation
2. Has developed an app leveraging FHIR resources and has broad deployments
I don't think folks who are using/developing against FHIR for in-house development/deployment have the same concerns/constraints/etc here (it is certainly not as pressing as the latter groups)
Kevin Shekleton (Jul 25 2017 at 21:53):
I agree that having the Argonauts all agree to move to STU3 on a defined timeframe would be great.
Kevin Shekleton (Jul 25 2017 at 21:54):
This really does become quite a large resourcing (time + people) problem as both vendors and app developers codebase and support for FHIR broadens.
Kevin Shekleton (Jul 25 2017 at 21:58):
The comments from Abigail on this Zulip thread from back in May really touch on the issues here. These issues aren't isolated to the EHR vendors.
Grahame Grieve (Jul 25 2017 at 22:10):
no, but the answer to them will be different for the argonaut community than they will be for e.g. the Australian national terminology service
Kevin Shekleton (Jul 25 2017 at 22:16):
Agreed
Last updated: Apr 12 2022 at 19:14 UTC
