Loading...
Help
Login
Busy
Search
Resume Patient - Templates

 
Template locked

OK Not OK
Templates (External repositories)

Warning Ok
Warning
Filter
eHDSI Allergies and Intolerances Entry
Issues (7)
Change Request Status = Open (lux-gh-issue-36): ValueSet definition for code element needed
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2018-05-08 14:15:48: Tracking by Heiko
Description
Finding:

- Different types of event types for the Allergy should come from ValueSet

Suggestion:

- Take SNOMED-CT codes as in AdverseEventType

Further explanation:

-

Change Request Status = Open (lux-gh-issue-37): value Element cardinality
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2018-05-08 15:27:00: Tracking by Heiko
Description
Finding:

- In eHDSI specifications we see cardinality as 0..*, whereas we change to 1..1 as it seems more reasonable for us

Suggestion:

- We keep 1..1 and will see Feedback from eHDSI PS specification https://ec.europa.eu/cefdigital/tracker/browse/EHOPERATIONS-378

Further explanation:

-

Change Request Status = Open (lux-gh-issue-38): Create valueSet for value Element
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2018-05-08 15:33:38: Tracking by Heiko
Description
Finding:

- For the Lux representation, create a value set which contains the list of allergies/problems, if possible

Suggestion:

-

Further explanation:

-

Change Request Status = Open (lux-gh-issue-39): Add Schematron rule on participant
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2018-05-08 16:19:08: Tracking by Heiko
Description
Finding:

- For enabling the constraint

Suggestion:

- Add Schematron assert

Further explanation:

-

Change Request Status = Open (lux-gh-issue-43): Add a valueSet for the Allergen
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2018-06-13 09:08:27: Tracking by Heiko
Description
Finding:

- playingEntity/code

Suggestion:

-

Further explanation:

-

Change Request Status = Open (lux-gh-issue-44): Problem entry relationship
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2018-06-13 11:55:41: Tracking by Heiko
Description
Finding:

-Note: the 1.3.6.1.4.1.19376.1.5.3.1.4.5 requires that also the template ID '2.16.840.1.113883.10.20.1.28' is included.


Suggestion:

- Should also be  2.16.840.1.113883.10.20.1.54 additionally to signalize that this is an allergic reaction

Problem entry element now contains as well the templateId 2.16.840.1.113883.10.20.1.54 optionally, means it would possibly make sense to add a Schematron rule here to ensure that in such cases the templateId within the problem entry shall be set.


Further explanation:

- In Problem entry now there is a constraint on the second templateId, maybe it is needed to add an additional check constraint on the entryRelationship to verify that the right templateId is used below.

Change Request Status = Open (lux-gh-issue-51): Value Sets assignment
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2019-01-09 14:17:24: Tracking by Heiko
Description
Finding:

-

Suggestion:

- Assign Valueset for Participant/code
- Create own ValueSet for the others which currently refer to eHDSI ones

Further explanation:

-

 
 
Busy
Structure Definitions (External repositories)