Loading...
Help
Login
Busy
Search
epSOS - Issues
 
Select object
Results (1 / 1)
Id Issue Status Priority Type Date Assigned To Label
271Implement changes related to Approved CP-018ClosedHighChange Request2018-05-18 12:18:18Mathias Ghys
 
Change RequestImplement changes related to Approved CP-018
Idepsos-issue-271
StatusClosed
PriorityHigh
Last Tracking2018-05-18 12:18:18  by  Mathias Ghys
Current AssigneeMathias Ghys
    
Concerns
Template
epSOS-ePrescription (epSOS ePrescription)
/
/
Template1.3.6.1.4.1.12559.11.10.1.3.1.1.1 (2013-12-20) epSOS-ePrescription
StatusDraft

/
-
/
-

Events
TrackingClosed2018-05-18 12:18:18: Tracking by Mathias Ghys
Edited byGiorgio Cangioli (2018-05-18 16:00:51)
Description
I implemented all the requested changes, except for:

  •  the line:

- The prescription ID must be the same as the prescription ID defined in the document header (document ID).


Christof Gessner put the following remark:
            
In Section 6 it is proposed to add a constraint to template 1.3.6.1.4.1.12559.11.10.1.3.1.3.2 requiring the prescription ID to be equal to the document ID. I don't think this is required, and I even would say it is wrong. Because the two IDs do not represent the same information object, not even the same kind of information object. A document that represents a prescription is not identical to the prescription itself. And I believe we would lose flexibility if we would consider these two objects to be identical.

Giorgio Cangioli: +1. The use of the ClincalDocument.id as prescription.id is a recurring error that again and again shows up. I don't like (and IMHO it is not correct as well ) either the section.id for this scope, but at least it provides some kind of flexibility...

  • The line

- Rename the template http://art-decor.org/art-decor/decor-templates--epsos-?id=2.16.840.1.113883.3.1937.777.11.10.144 “epSOS Related Prescription Item” to “eHealth DSI Related Prescription”


I agree with this request, but for reasons of consistency, I won't perform the change now, since we will have some templates with eHealth DSI, and others with epSOS in the name. I think it would be more logic to change them all at once.



Assignment2018-05-18 10:58:23: Assigned To Mathias Ghys by Mathias Ghys
TrackingOpen2018-05-18 10:58:22: Tracking by Mathias Ghys
Description
Suggestion:

- From the approved CP-018:

In the ART-DECOR template for ePrescription document http://art-decor.org/art-decor/decor-templates--epsos-?id=1.3.6.1.4.1.12559.11.10.1.3.1.1.1 alter the cardinality of the elementhl7:component/hl7:structuredBody/hl7:component from the current 1...* to 1...1.In   the template http://art-decor.org/art-decor/decor-templates--epsos-?id=1.3.6.1.4.1.12559.11.10.1.3.1.2.1 of the    Section Prescription alter the cardinality of the elementhl7:section from 0...* to 1...1. In the same template alter the cardinality of the  element hl7:section/hl7:entry from 1...* to 1...1.In   the template for epSOS CDA substanceAdministration http://art-decor.org/art-decor/decor-templates--epsos-?section=templates&id=1.3.6.1.4.1.12559.11.10.1.3.1.3.2 replace the description ofthe element hl7:id by the  following: “Prescription ID. The following must be true: - The prescription ID must be globally unique.- The prescription ID must be the same as the prescription ID defined in the document header (document ID).- The prescription ID can be used by the prescribing system or provider to identify the  prescription to which it belongs. This provides the link from the dispensed medicine to the prescription.”

In the ART-DECOR template for eDispensation http://art-decor.org/art-decor/decor-templates--epsos-?section=templates&id=1.3.6.1.4.1.12559.11.10.1.3.1.1.2 alter the cardinality of    the elementhl7:component/hl7:structuredBody/hl7:component from the current 1...* to 1...1.In   the template http://art-decor.org/art-decor/decor-templates--epsos-?id=1.3.6.1.4.1.12559.11.10.1.3.1.2.2 of the    Section Dispensation alter the cardinality of the elementhl7:section/hl7:entry from 1...* to 1...1.In   the template http://art-decor.org/art-decor/decor-templates--epsos-?id=1.3.6.1.4.1.12559.11.10.1.3.1.3.3 for epSOS CDA Supply alter the cardinality of the element hl7:supply from 0...* to 1...1. In the same template replace the description of the first instance of the element hl7:entryRelationship by the following:“Related PrescriptionThe related prescription is represented via an entry relationship of type code "REFR", and containing a  prescription entry as described in section 12.1.2.4. The prescription ID is required within the Dispensed Medication Entry.

Contains 2.16.840.1.113883.3.1937.777.11.10.144 epSOS Related Prescription (DYNAMIC)”Rename the template http://art-decor.org/art-decor/decor-templates--epsos-?id=2.16.840.1.113883.3.1937.777.11.10.144 “epSOS Related Prescription Item” to “eHealth DSI Related Prescription”. In the ART-DECOR template

for ePrescription document
http://art-decor.org/art-decor/decor-
templates--epsos-?id=1.3.6.1.4.1.12559.11.10.1.3.1.1.1 alter the cardinality
of the element
hl7:component/hl7:structuredBody/hl7:component from the
current 1...* to 1...1.
In the template http://art-decor.org/art-decor/decor-templates--epsos-
?id=1.3.6.1.4.1.12559.11.10.1.3.1.2.1
of the Section
Prescription alter the cardinality
of the element
hl7:section
from
0...* to 1...1.
In the
same template
alter
the cardinality of
the element
hl7:section/hl7:entry
from
1...*
to 1...1.
In the template for epSOS
CDA substanceAdministration http://art-decor.org/art-decor/decor-
templates--epsos-?section=templates&id=1.3.6.1.4.1.12559.11.10.1.3.1.3.2 replace the description of
the element
hl7:id by
the following:
“Prescription ID. The following
must be true:
- The prescription ID
must be globally unique.
- The prescription ID
must be the
same
as the prescription ID defined in the document header
(document
ID).
- The prescription ID
can be
used
by the
prescribing
system
or provider to identify
the prescription to
which it belongs. This provides the
link from
the dispensed
medicine to the prescription.”
    
Labels
PreviewCodeHTML colorDisplay NameDescription
 
 TBA 
TBATBATo be approved
To be discussed and approved
 
 M1 
M1M1Milestone 1
Milestone 1 – before the EXPAND-athon 9-12 December 2015 Lisbon
 
 M2 
M2M2Milestone 2
Milestone 2 – final results to be delived at the end of EXPAND
 
 M3 
M3M3Milestone 3
Milestone 3 – end of the HL7 International Project
 
 M4 
M4M4Milestone 4
Milestone 4 – for consideration in the future / desiderata
 
 WJ 
WJWJChanges Word/JIRA
Changes in the Word Specification/Open a JIRA issue
 
 TID 
TIDTIDTemplate ID
Template-ID changes throughout the specification