Loading...
Help
Login
Busy
Search
eHDSI - Templates
 
Template locked

OK Not OK
Templates (External repositories)

Warning Ok
Warning
Filter
Medication Item
Issues (12)
Change Request Status = Closed (epsos-issue-100): rename to "Medication Item""
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Current Labels
 
 (M2) Milestone 2 
Events
Tracking / Status = Closed 2015-11-24 18:53:57: Tracking by Dr. Kai U. Heitmann
 
 M2 
Description
The Template's business name and display name has been set accordingly
Assignment2015-11-24 17:15:11: Assigned To Dr. Kai U. Heitmann by Christof Gessner
 
 M2 
Tracking / Status = Open 2015-11-24 17:15:10: Tracking by Christof Gessner
 
 M2 
Description
Finding:

- epSOS uses the name " Medication Item " for this template, In IHE OCC it is named "Medications"

Suggestion:

- replace " EntryMedicationSummary "  with "Medication Item" to be consistent with epSOS

Further explanation:

-

Request for Information/Education Status = Deferred (epsos-issue-101): templates for Normal Dosing, split dosing and combination medication
TypeRequest for Information/EducationStatusRequest for Information/Education Status = Deferred PriorityLow
Current Labels
 
 (M2) Milestone 2 
Events
Tracking / Status = Deferred 2017-05-17 13:54:38: Tracking by Giorgio Cangioli
 
 M2 
Description
In case to be reconsidered for future discussion
Tracking / Status = Open 2016-03-01 12:48:46: Tracking by Giorgio Cangioli
 
 M2 
Description
Look at the ELGA medication specs where they have description about it
Assignment2015-11-24 18:48:50: Assigned To Christof Gessner by Dr. Kai U. Heitmann
 
 M2 
Tracking / Status = Open 2015-11-24 18:42:22: Tracking by Dr. Kai U. Heitmann
 
 M2 
Description
The set of template IDs A, B, C etc here used in an instance mean: My instance is conformant to Template A, B and C etc.

What the optional template IDs mean here is the following (one as an example):

IF my instance is A "normal" <substanceAdministration> act that may not contain any subordinate <substanceAdministration> acts
THEN I must indicate that in my instance by mentioning template ID 1.3.6.1.4.1.19376.1.5.3.1.4.7.1
ELSE don't mention it (i.e. my instance fragment is NOT a "normal substanceAdministration"

Make this the thing more clear?

Assignment2015-11-24 17:24:00: Assigned To Dr. Kai U. Heitmann by Christof Gessner
 
 M2 
Tracking / Status = Open 2015-11-24 17:23:59: Tracking by Christof Gessner
 
 M2 
Description
Finding:

- three template IDs are given as optional

Suggestion:

- seeking clarification if that is the correct way to express this. Are the templates mutually exclusive? Any formal rules to be added?

Further explanation:

-

Change Request Status = Closed (epsos-issue-149): Value set 2.16.840.1.113883.1.11.19708 ActSubstanceAdministrationCode
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-05-17 09:57:34: Tracking by Giorgio Cangioli
Description
Binding removed
Tracking / Status = Open 2016-11-14 22:47:52: Tracking by Dr. Kai U. Heitmann
Description
What do you suggest? Delete that binding?
Tracking / Status = Open 2016-11-14 17:38:22: Tracking by Giorgio Cangioli
Description
Finding:

The adoption of this Value set 2.16.840.1.113883.1.11.19708 ActSubstanceAdministrationCode has been never discussed in epSOS or EXPAND

Suggestion:

-

Further explanation:

-

Change Request Status = Closed (epsos-issue-151): statusCode cardinality to 1..1
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-05-17 09:54:40: Tracking by Giorgio Cangioli
Description
fixed to 1..1
Tracking / Status = Open 2016-11-24 10:44:45: Tracking by Giorgio Cangioli
Description
Finding:

Fix the statusCode cardinality to 1...1

Suggestion:

-

Further explanation:

-

Change Request Status = Closed (epsos-issue-152): IHE PCC templateId entry cannot be required
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-05-17 09:30:56: Tracking by Giorgio Cangioli
Description
changed cardinality of the "other" templates to 0..1
Tracking / Status = Open 2016-11-24 10:46:21: Tracking by Giorgio Cangioli
Description
Finding:

In the case of statusCode <> completed the template is not compliant with the IHE PCC template.
so this id cannot be required.

Suggestion:

-

Further explanation:

-

Change Request Status = Deferred (epsos-issue-153): Example: Invalid XML
TypeChange RequestStatusChange Request Status = Deferred PriorityLow
Events
Tracking / Status = Deferred 2017-05-17 14:52:25: Tracking by Giorgio Cangioli
Description
no more able to see where the problem was...maybe it has been fixed
Tracking / Status = Open 2016-11-24 11:13:54: Tracking by Giorgio Cangioli
Description
Finding:

Fix the Example => Invalid XML

Suggestion:

-

Further explanation:

-

Change Request Status = Closed (epsos-issue-154): Update the doseQuantity description
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-05-17 09:50:00: Tracking by Giorgio Cangioli
Description
description updated
Tracking / Status = Open 2016-11-24 11:15:07: Tracking by Giorgio Cangioli
Description
Finding:

Update the doseQuantity description to 

"The dose is specified in the <doseQuantity> element.

If a dose range is given (e.g., 1-2 tablets, or 325-750mg), then the <low> and <high> bounds are specified in their respective elements...

If the dose is in countable items (tablets, caplets, "eaches"), then the unit should be valorized  = ‘1’. In this case it is allowed to used the UCUM annotations for describing the type of countable items (e.g. .{tablet}, {puff},..).

The unit attribute – when expresses unit of measures- shall be derived from the Value Sets epSOSUnits, 1.3.6.1.4.1.12559.11.10.1.3.1.42.16 based on the UCUM code system.  The countable units attribute is derived from the value set epSOSDoseForm, OID 1.3.6.1.4.1.12559.11.10.1.3.1.42.2."

Suggestion:

-

Further explanation:

-

Request for Information/Education Status = Closed (epsos-issue-155): Clarification on the usage of doseQuanity
TypeRequest for Information/EducationStatusRequest for Information/Education Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-05-17 09:51:17: Tracking by Giorgio Cangioli
Description
Updated the doseQuantity description
Tracking / Status = Open 2016-11-24 11:16:30: Tracking by Giorgio Cangioli
Description
Finding:

Make clear that according the latest specifications both IVL_PQ and PQ are allowed

Suggestion:

-

Further explanation:

-

Change Request Status = Closed (epsos-issue-171): multiple instances of effectiveTime
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Current Labels
 
 (TBA) To be approved 
Events
Tracking / Status = Closed 2019-12-23 13:37:08: Tracking by Mathias Ghys
 
 TBA 
Description
This issue is solved by adding the datatype to the effectiveTime elements: 
  • For the first effectiveTime (duration of treatment): where [@xsi:type='IVL_TS']
  • For the second effectiveTime (frequency of intakes): 
  • where [@value or @nullFlavor]
  • where  [@xsi:type='PIVL_TS']
  • where  [@xsi:type='EIVL_TS']
  • where  [@xsi:type='SXPR_TS']
Assignment2017-07-18 23:21:44: Assigned To Christof Gessner by Christof Gessner
 
 TBA 
Tracking / Status = Open 2017-05-23 21:36:14: Tracking by Christof Gessner
 
 TBA 
Description
Finding:

-validation fails for multiple effectiveTime instances. But epSOS requires two instances, at least in some cases. Note: this will probably be fixed by epsos-issue-101.

Suggestion:

- add more specific information on occurrence, like effectiveTime[1], effectiveTime[2] etc.

Further explanation:

-

Change Request Status = Open (epsos-issue-188): Dosing-specific templates do not appear in template ID list
TypeChange RequestStatusChange Request Status = Open PriorityLow
Current Labels
 
 (TBA) To be approved 
Events
Tracking / Status = Open 2017-07-18 15:21:05: Tracking by Giorgio Cangioli
 
 TBA 
Description
Since this template needs to be revised in order to be specialized depending on the fact is used in a eP or into a PS.

I Suggest to postpone this issue and when the revision will be done do no consider anymore these templates but use of the subordinated substance administration as suggested by the medication statement template defined by the Phama WG and adopted for the IPS
Tracking / Status = Open 2017-07-17 12:49:41: Tracking by Dr. Kai U. Heitmann
 
 TBA 
Description
These templates are not defined (in the project) but included as a reference only in the instance (templateId). The text should be updated to reflect this difference, i.e. the boldfaced heading shall not include any template id and the text should read something like "in order to indicate conformance to the underlying IHE template, a templateId element is specified in the instance"... 
Assignment2017-07-17 11:33:46: Assigned To Dr. Kai U. Heitmann by Christof Gessner
 
 TBA 
Tracking / Status = Open 2017-07-17 11:33:45: Tracking by Christof Gessner
 
 TBA 
Description
Finding:

- The 3 dosing-specific templates do not appear in template ID list. This might make it difficult for implementers/users to locate the related constraints. 

Suggestion:

-

Further explanation:

-

Request for Information/Education Status = Closed (epsos-issue-195): XML namespace for epSOS medication extensions
TypeRequest for Information/EducationStatusRequest for Information/Education Status = Closed PriorityHigh
Current Labels
 
 (TBA) To be approved 
Events
Tracking / Status = Closed 2017-07-27 20:36:16: Tracking by Dr. Kai U. Heitmann
 
 TBA 
Description
Changed to urn:epsos-org:ep:medication
Assignment2017-07-27 17:53:48: Assigned To Dr. Kai U. Heitmann by Christof Gessner
 
 TBA 
Tracking / Status = In Progress 2017-07-27 17:53:19: Tracking by Christof Gessner
 
 TBA 
Description
For an unknown reason the epSOS templates in ART-DECOR define xmlns:epsos="urn:epSOS:ps:ps:2010".
This is in contradiction to the specifications in the previous versions (i. e. PDF) where xmlns:epsos="urn:epsos-org:ep:medication".
The schemas contained in the OpenNCP distribution also define xmlns:epsos="urn:epsos-org:ep:medication".

Suggestion to change this in eP, eD and PS specifications of this project to uniformly use xmlns:epsos="urn:epsos-org:ep:medication"
Tracking / Status = Open 2017-07-22 11:44:21: Tracking by Dr. Kai U. Heitmann
 
 TBA 
Description
While it is valid to use different namespaces with the same prefix (epsos:), we do not recommend that. In addition, this is impossible in an ART-DECOR project containing both namespaces with the same prefix.
I am unsure about the rationale as all those things have been intended to be extensions defined within the epSOS project. the "ps" let me assume that this is a patient summary namespace only.
Also from a W3C schema perspective it is better to not add too many extra namespaces to it.
Also I am unsure whether format codes necessarily need to be linked to namespaces.
Tracking / Status = Open 2017-07-22 09:57:10: Tracking by Giorgio Cangioli
 
 TBA 
Description
Yes the urn:epsos:ps:ps:2010 is urn the formatCode for the XC* transactions

From the word based specifications
"For the purposes of WP 3.5 this extension is necessary to satisfy the requirements for eP and eD data elements to represent a generic equivalent and ingredients.

The rules of section 1.4 CDA Extensibility require the designation of a new XML namespace for the XML elements in this structure. For the purposes of documentation, the namespace urn:epsos-org:ep:medication shall be used."

Assignment2017-07-19 14:56:00: Assigned To Christof Gessner by Christof Gessner
 
 TBA 
Tracking / Status = Open 2017-07-19 14:55:59: Tracking by Christof Gessner
 
 TBA 
Description
Finding:

- There is a conflict between the namespace declaration here and the specifications: According to the PDF-spec and the schemas it should be "urn:epsos-org:ep:medication", but here it is declared as "urn:epsos:ps:ps:2010". This is inconsistent with the schemas that are currently distributed with OpenNCP.

Suggestion:

- Before changing the namespace uri here in the templates, it should be clarified if there could be are any side effects of such a change.
Suspects are e.g. XCF implementations that used "urn:epsos:ps:ps:2010" as formatCode metadata entry (see https://gazelle.ihe.net/node/133).

Further explanation:

-

Change Request Status = Open (epsos-issue-199): doseQuantity: value set binding for units
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Current Labels
 
 (TBA) To be approved 
Events
Tracking / Status = Open 2017-07-27 20:46:38: Tracking by Christof Gessner
 
 TBA 
Description
I suggest to remove the requirement to have a unit attribute.
a) in the present form it precludes the use of IVL_PQ (with low and/or high elements)
b) In section 11.1.1.2.3. of the PDF spec for the case of "countable items" it is stated that "In this case, only the unit count is specified , no units are specified." (which I prefer over the curly bracket kludge)
c) the value set binding has to be discussed in the light of the option to use those curly brace expressions. Probably needs to be CWE, so we get schematron warnings, but not errors.
Tracking / Status = Open 2017-07-27 20:30:22: Tracking by Dr. Kai U. Heitmann
 
 TBA 
Description
Create a choice.
As just discussed a data type (flavour) like PQ.EPSOS lives outside this project (and maybe even governance groups) and would have the need to access the bound value set from anywhere (e.g. use the internet to access ART-DECOR terminology services). This seems to be not very practical. 
Tracking / Status = Open 2017-07-27 20:06:17: Tracking by Christof Gessner
 
 TBA 
Description
Finding:

- The requirement to have a unit attribute in doseQuantity is conflicting with the rule "both IVL_PQ and PQ are allowed" (see also epsos-issue-155)

Suggestion:

- create a choice construct between PQ and IVL_PQ. 
OR, preferrably, move the value set binding to a constrained PQ data type like "PQ.EPSOS"

Further explanation:

-

 
 
Busy
Structure Definitions (External repositories)