Help
Login
Busy
Search
CDA-CH-EMED eMedication - Value Sets

 
Valueset locked

Value Sets (External repositories)
/
-
Warning Ok
Warning
true50
TimingEvent
false
Issues (4)
false
Change Request Status = Closed ( chdachpharm-issue-20 ): TimingEvent VS differs from EventTiming in CH EMED
Type Change Request Status Change Request Status = Closed Priority Normal
Events
Tracking / Status = Closed 2021-06-07 18:12:24 : Tracking by Annatina Foppa
Description
- additional minor changes: label, codeSystem and level/type changed
Assignment 2021-06-07 16:40:34 : Assigned To Patrick Jolo by Annatina Foppa
Tracking / Status = Feedback needed 2021-06-07 15:09:11 : Tracking by Patrick Jolo
Description
-Value Set updated
-Translations added

Assignment 2021-03-21 11:08:48 : Assigned To Pero Grgic by Annatina Foppa
Description
discussed 17.3. with Cara & ahdis, decision taken: use HL7 FHIR value set  Valueset-event-timing - FHIR v4.0.1 (hl7.org)  also in CDA
Tracking / Status = Open 2021-02-18 17:46:15 : Tracking by Annatina Foppa
Description
Finding:

At the projectathon 2020, the following problem popped up: The value set for timing event (such as before meal. After meal etc.) is not the same in FHIR and CDA-CH-EMED. But both value sets are required (by FHIR and IHE PCC, respectively)

Suggestion:

- inquire on the international level to resolve this issue

Further explanation:

-

Change Request Status = Closed ( chdachpharm-issue-32 ): remove duplicate value set
Type Change Request Status Change Request Status = Closed Priority Normal
Events
Tracking / Status = Closed 2021-06-02 18:57:27 : Tracking by Annatina Foppa
Description
added reference to value set 2. "duplicate" is original value set of HL7 v3, not referenced anymore. Ticket closed.
Tracking / Status = Feedback needed 2021-06-02 18:40:02 : Tracking by Pero Grgic
Description
In project CH-EMED the reference to the value set  TimingEvent of project CH-PHARM is removed.
Assignment 2021-03-16 12:26:07 : Assigned To Pero Grgic by Annatina Foppa
Tracking / Status = Open 2021-03-16 12:26:06 : Tracking by Annatina Foppa
Description
Finding:

- from Rafael Jimenez, May 2020: - Found two valueSet from different source.

1) From list a valueSet (https://art-decor.org/art-decor/decor-valuesets--cdachemed-)

ID: 2.16.840.1.113883.1.11.10706 with name : TimingEvent (http://art-decor.org/decor/services/RetrieveValueSet?prefix=cdachemed-&language=en-US&version=&id=2.16.840.1.113883.1.11.10706&effectiveDate=dynamic&format=xml)

2) From "CDA EMED templates" ID :2.16.756.5.30.1.127.77.4.11.2 with

name : CH-EMED-TimingEvent (http://art-decor.org/decor/services/RetrieveValueSet?prefix=cdachemed-&language=en-US&version=&id=2.16.756.5.30.1.127.77.4.11.2&effectiveDate=dynamic&format=xml)                        

- no description

- no translation


Suggestion:

- remove first value set (it can still be found, or is this for historical purposes?)

Further explanation:

- comes from Gazelle ticket, the other points have been addressed separately: [EHS-326] Missing translation in TimingEvent valueset - Gazelle (ihe.net)

Change Request Status = Closed ( chdachpharm-issue-48 ): TimingEvent: missing values from the HL7v3 value set
Type Change Request Status Change Request Status = Closed Priority Normal
Events
Tracking / Status = Closed 2021-06-10 08:23:17 : Tracking by Annatina Foppa
Description
Yes, that is on purpose. That was the point what made the discussion so difficult: that v3 TimingEvent was not a genuine subset of FHIR EventTiming, but had this additional terms. The decision was to use FHIR VS in place of v3.
Assignment 2021-06-08 20:10:30 : Assigned To Pero Grgic by Quentin Ligier
Tracking / Status = Open 2021-06-08 20:10:29 : Tracking by Quentin Ligier
Description
Some values of the HL7v3 TimingEvent value set are absent here: IC, ICD, ICM, ICV (between meals). Is it voluntary?
Change Request Status = Closed ( chdachpharm-issue-62 ): Reduction of the TimingEvent value set
Type Change Request Status Change Request Status = Closed Priority Normal
Events
Tracking / Status = Closed 2022-04-19 10:35:08 : Tracking by Quentin Ligier
Tracking / Status = Open 2022-04-19 10:34:38 : Tracking by Quentin Ligier
Description
Value set  TimingEventAmbu  created in CDA-CH-EMED for the use of the aggregator only. The templates are not modified to use it. It's done for documentation and code generation only.
Tracking / Status = Open 2022-02-10 11:45:41 : Tracking by Patrick Jolo
Description
After internal discussion:
This ValueSet is from FHIR Standard. We do not want to differ from the standard.  A recommendation is made in the FHIR IG: 
For the representation of the time of administration according to the 1-1-1 scheme, the values MORN-NOON-EVE-NIGHT from the ValueSet EventTiming are highly recommended for the Swiss use.

Therefore, this ValueSet will not be adjusted.
A reduction would have to be discussed in a larger discussion.

If this is good for you then I close the issue or set to "For future consideration"
Tracking / Status = Open 2022-02-02 11:13:50 : Tracking by Quentin Ligier
Description

The timing event value set currently has 26 codes, few of those are currently used in real life. They pose an issue for representing them on a medication card: while the four usual codes (morning, noon, evening and night) have a simple representation made of four consecutive boxes, others have not and will probably have to be represented in narrative text.

The “Universal medication schedule” – with its common representation of the four usual codes (morning, noon, evening, night) – has been promoted worldwide for safe medication use. It has showed to reduce the risk of confusion and covers about 90% of medication prescribed (e.g. this article among others: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5130952/). It should be the priority. Therefore, we argue to focus on the 4 codes which have a proven and great impact on quality of care, while dropping the other codes which raise the difficulties of implementing the exchange format.

Consequences of status quo are high difficulties for integration to interpret and match codes. This  seriously impacts its uptake, and, most of all, increase the risks of errors induced by technologies. Such a long and complex value set impacts usability by clinicians (cognitive-burden, time-consuming).

At the same time, we encourage eHealth Suisse and software providers to invest a continuous effort aiming to improve the quality of patient instructions. Some expansions have been more recently proposed for other drug formulation (e.g. drops, inhalator) based on health literacy principles. (See : https://bmjopen.bmj.com/content/4/1/e003699).

Propositions:

1.     Value set TimingEvent : only keep the values “Morning (MORN)”, “Noon (NOON)”, “Evening (EVE)” and “Night (NIGHT)”, encouraging their use.

2.     Other notions (with food/drink, before/after meal) appear as comments.

3.     The common representation for these dosages (in the narrative text) is the usual 4 boxes one.

4.     Other timing events and more complex dosages are described in the non-structured dosage instructions entry.

5.     These changes may be temporary or definitive. Evolution may be proposed later as part of an appropriate change management program aiming to achieve health literacy standards and guidelines in collaboration with industry and policy-maker.

Drafted by HUG and CARA.

 
 
false
Usage (…)
Busy Retrieving…
Busy