Help
Login
Busy
Search
epSOS - Issues

 
Select object
 
falsehide
Results (1 / 1)
Id Issue Status Priority Type Date Assigned To Label
262 Adapt examples according to specification Closed Normal Change Request 2018-03-14 16:18:31 Mathias Ghys
 
 TBA 
 
Change Request Adapt examples according to specification
Id epsos-issue-262
Status Closed
Priority Normal
Last Tracking 2018-03-14 16:18:31  by  Mathias Ghys
Current Assignee Mathias Ghys
Current Labels
    
 (TBA) To be approved 
    
Concerns
Template
false
epSOS CDA Supply (1.3.6.1.4.1.12559.11.10.1.3.1.3.3)
/
/
Template 1.3.6.1.4.1.12559.11.10.1.3.1.3.3 (2013-12-20) epSOS CDA Supply
Status Draft
/
-
/
-
Events
Tracking Closed 2018-03-14 16:18:31 : Tracking by Mathias Ghys
    
 TBA 
Description
We received the confirmation in the semantic group in the meeting of 14/3 to change the moodCode attribute and it has been adapted.
Tracking Feedback needed 2018-02-16 09:50:05 : Tracking by Mathias Ghys
    
 TBA 
Description
I reverted the changes to 'EVN'.
Although the solution is that the moodCode has to be changed to 'INT', there is an impact on the implementation and the national implementation of the countries.
A JIRA ticket is created in our backlog for follow up: https://ec.europa.eu/cefdigital/tracker/projects/EHSEMANTIC/issues/EHSEMANTIC-215
Tracking Feedback needed 2018-02-14 09:47:16 : Tracking by Mathias Ghys
    
 TBA 
Description
Feedback from Giorgio Cangioli:

"The supply that describes what have been dispensed is an EVN (I see however that the template is more generic and allow both EVN and INT)
The referred SubstanceAdministration describes the intent of taking a drug ( in this sense its id correspond to the prescribed item ID) so its moodCode should be INT."

After some clarification and explanation by Giorgio, I decided to change the moodCode from 'EVN' to 'INT' and adapt the examples
Tracking Feedback needed 2018-02-13 16:26:08 : Tracking by Mathias Ghys
Edited by Mathias Ghys ( 2018-02-13 16:27:56 ) Mathias Ghys ( 2018-02-13 16:28:12 )
Description

Dear Giorgio,

First of all thank you very much for your reply. Your knowledge is highly appreciated!

Just to get my understanding right (so that we are talking about the same thing):

In my understanding:

  • INT = INTENT = a medication has been prescribed and the INTEND is there that the patient will
  • EVN = the administration of the dispensed drugs.

The epSOS Related Prescription Item template is the template in the eDispensation that tracks back to the initial ePrescription.

From this viewpoint I totally agree with you that the @moodCode has to be changed to INT in the specification, the example and the description.

Do you agree if I adapt it?

Tracking Feedback needed 2018-02-13 11:26:40 : Tracking by Giorgio Cangioli
Description
"The moodCode of the substanceAdministration will always have the value 'EVN' since the prescription has already been filled at the moment of the dispensation."

No EVN in this case means that the drug has been administrated not that the prescription has been dispensed !

the supply(EVN) says this...

So in the 99% of the cases it is correct to leave this as INT, unless you have a system that tracks the administration of the dispensed drugs...
Tracking Closed 2018-02-13 11:10:31 : Tracking by Mathias Ghys
Description
I adapted the examples. There is no risk in doing so and it will make the documentation a lot clearer for the users.
Assignment 2018-02-13 10:43:54 : Assigned To Mathias Ghys by Mathias Ghys
Tracking Open 2018-02-13 10:43:53 : Tracking by Mathias Ghys
Description
Finding:

- For the Related prescription item, the moodCode is defined to be "EVN" in the specifications, but in the examples, "INT" is used. Since the moodCode attribute shall be INT to reflect that a medication has been prescribed, or EVN to indicate that the prescription has been filled, it has to be EVN because it is part of the eDispensation message.

Suggestion:

- Change the moodCode in the examples from "INT" to "EVN"

Further explanation:

-

    
Labels
Preview Code HTML color Display Name Description
 
 TBA 
TBA TBA To be approved
To be discussed and approved
 
 M1 
M1 M1 Milestone 1
Milestone 1 – before the EXPAND-athon 9-12 December 2015 Lisbon
 
 M2 
M2 M2 Milestone 2
Milestone 2 – final results to be delived at the end of EXPAND
 
 M3 
M3 M3 Milestone 3
Milestone 3 – end of the HL7 International Project
 
 M4 
M4 M4 Milestone 4
Milestone 4 – for consideration in the future / desiderata
 
 WJ 
WJ WJ Changes Word/JIRA
Changes in the Word Specification/Open a JIRA issue
 
 TID 
TID TID Template ID
Template-ID changes throughout the specification