Stream: cds hooks/github
Topic: docs / Issue #78 Support for non-FHIR clinical models
Github Notifications (Aug 23 2017 at 06:50):
rongchen opened Issue #78
We build cds-services for local EMR/GP systems in Nordic market, and are very interested in the cds-hooks design. However given FHIR adoption rate for real-use is currently very low here in this part of the world, having cds-hooks hard-wired to FHIR resources would significantly increase the barrier for its use.
From a design point of view, cds-hooks can work equally well with other standardized non-FHIR clinical models such as openEHR archetypes, CIMI and EN13606. Is there any plan to allow such extension in the future?
Github Notifications (Sep 05 2017 at 20:30):
bdoolittle commented on Issue #78
At its heart, CDS-Hooks is a standard for the event-based invocation of remote services. It does not need to be tightly coupled to any single data model, but I imagine that there would be a tradeoff between the number of data models supported by CDS-Hooks and the interoperability it grants. In the short term, it's important to not over complicate the standard so that the 1.0 version can get off the ground. In the long run, decoupling CDS-Hooks from it's underlying data model seems generally like a good idea as standards always change.
You should not feel limited by CDS-Hooks being hard-wired to FHIR. The standard can be extended to use a different data model, it just requires an integration between CDS Provider and EHR.
Github Notifications (Sep 09 2017 at 09:51):
rongchen commented on Issue #78
Well said.
Github Notifications (Sep 09 2017 at 09:53):
grahamegrieve commented on Issue #78
given that cds-hooks is open, the likely thing to do is to fork the source, adapt it to openEHR, and see how close you can keep to the original. Then you'll have a solid base for bringing change proposals to the spec
Github Notifications (Sep 10 2017 at 09:49):
rongchen commented on Issue #78
@grahamegrieve very good idea indeed. In fact, we really want to make CDS-Hooks work for openEHR as well as other standards or non-standards based EHRs.
Github Notifications (Sep 14 2017 at 08:06):
isaacvetter commented on Issue #78
@rongchen - it sounds like you got an answer that made you happy - closing.
@brian doolittle - I think that #76 better captures your concern, and note that it's also marked as 1.0. Closing.
Github Notifications (Sep 14 2017 at 08:06):
isaacvetter closed Issue #78
Last updated: Apr 12 2022 at 19:14 UTC
