Stream: cds hooks/github
Topic: docs / Issue #52 Terminology for EHR triggers
Github Notifications (Jun 07 2017 at 19:05):
gdelfiol opened Issue #52
Is there a plan to define a controlled terminology for EHR triggers of CDS Hooks? Options like “medication-prescribe” and “order-review” are strikingly similar to the HL7 ActTaskCode value set (https://www.hl7.org/fhir/v3/ActTaskCode/vs.html) within the HL7 ActCode code system. For example, "order-review" is "OREV" and "medication-prescribe" is "MEDOE". Why not just adapt the ActTaskCode value set for CDS Hooks?
Github Notifications (Aug 23 2017 at 06:30):
rongchen commented on Issue #52
In this 2009 paper, Clinical decision support capabilities of commercially-available clinical information systems, a list of common EHR triggers are listed. It seems to be good starting point.
Github Notifications (Sep 12 2017 at 19:19):
kpshek labeled Issue #52
Github Notifications (Sep 12 2017 at 19:31):
Per discussion at the Sept WGM (Tue Q2), we should encourage people creating hook definitions that the HL7 ActTaskCode value set exists. However, this value set may be more broad than what we are defining today with our hook definitions.
@gdelfiol brought up an excellent point that this value set was defined for Infobutton and allows new values to be defined outside of the Infobutton spec. CDS Hooks would benefit from externalizing the hook definitions outside of the spec so that new hook definitions don't require new CDS Hooks spec releases.
Github Notifications (Sep 12 2017 at 20:23):
grahamegrieve commented on Issue #52
HL7 has agreed to define a set of trigger codes. Some - or many - of these will be candidates for cds-hook definitions
Github Notifications (Dec 11 2017 at 21:29):
brynrhodes commented on Issue #52
Where is the work to define this set of triggers being done?
Github Notifications (Dec 11 2017 at 21:32):
gdelfiol commented on Issue #52
It’s done through HL7 harmonization, which happens before each HL7 WG. Requests are submitted offline and discussed in a conference call.
http://www.hl7.org/events/harmonization/index.cfm?ref=nav
http://wiki.hl7.org/index.php?title=Vocabulary_and_RIM_Harmonization_ProcessFrom: Bryn Rhodes <notifications@github.com>
Reply-To: cds-hooks/docs <reply@reply.github.com>
Date: Monday, December 11, 2017 at 2:29 PM
To: cds-hooks/docs <docs@noreply.github.com>
Cc: Guilherme Del Fiol <guilherme.delfiol@utah.edu>, Mention <mention@noreply.github.com>
Subject: Re: [cds-hooks/docs] Terminology for EHR triggers (#52)Where is the work to define this set of triggers being done?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/cds-hooks/docs/issues/52#issuecomment-350864158>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD6r2SUX8McXXi703KJla9O3FqIrZPDVks5s_Z7BgaJpZM4NzJbx>.
Github Notifications (Dec 11 2017 at 21:44):
brynrhodes commented on Issue #52
@gdelfiol, do you know whether the ActTaskCode value set was developed specifically for InfoButton, or was it already present and InfoButton used it?
Github Notifications (Dec 11 2017 at 22:38):
gdelfiol commented on Issue #52
It was initially developed for Infobutton (I presented the proposal at vocab harmonization), but then other groups proposed additions over time.
From: Bryn Rhodes <notifications@github.com>
Reply-To: cds-hooks/docs <reply@reply.github.com>
Date: Monday, December 11, 2017 at 2:44 PM
To: cds-hooks/docs <docs@noreply.github.com>
Cc: Guilherme Del Fiol <guilherme.delfiol@utah.edu>, Mention <mention@noreply.github.com>
Subject: Re: [cds-hooks/docs] Terminology for EHR triggers (#52)@gdelfiol<https://github.com/gdelfiol>, do you know whether the ActTaskCode value set was developed specifically for InfoButton, or was it already present and InfoButton used it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/cds-hooks/docs/issues/52#issuecomment-350868292>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD6r2WdelEp1fz22Airj5G6YSJVOKIx9ks5s_aJEgaJpZM4NzJbx>.
Github Notifications (Dec 11 2017 at 22:46):
brynrhodes commented on Issue #52
@gdelfiol, that's great! Do you have a sense for how well supported the codes are within EHR implementations? Do the InfoButton integrations actually implement workflow points at these codes?
Github Notifications (Dec 11 2017 at 22:50):
gdelfiol commented on Issue #52
I am familiar with the implementation in one EHR and it’s fairly good. It does not support all the codes on ActTaskCode, but the ones they use are correct. Knowledge vendors implemented them fairly well too. The most common ones that are supported are probably problem list review, problem list entry, laboratory results review, medication list review, and medication order entry.
From: Bryn Rhodes <notifications@github.com>
Reply-To: cds-hooks/docs <reply@reply.github.com>
Date: Monday, December 11, 2017 at 3:47 PM
To: cds-hooks/docs <docs@noreply.github.com>
Cc: Guilherme Del Fiol <guilherme.delfiol@utah.edu>, Mention <mention@noreply.github.com>
Subject: Re: [cds-hooks/docs] Terminology for EHR triggers (#52)@gdelfiol<https://github.com/gdelfiol>, that's great! Do you have a sense for how well supported the codes are within EHR implementations? Do the InfoButton integrations actually implement workflow points at these codes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/cds-hooks/docs/issues/52#issuecomment-350883739>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD6r2W4Xtjv8pDJM4K7JFZTJaq0jlYNJks5s_bC9gaJpZM4NzJbx>.
Last updated: Apr 12 2022 at 19:14 UTC
