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

 
Template locked

OK Not OK
Templates (External repositories)

Warning Ok
Warning
Filter
eHDSI Problem Entry
Issues (6)
Change Request Status = Closed (lux-gh-issue-41): Add ValueSet for code element
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2018-08-14 10:29:43: Tracking by Samuel
Description
used 1.3.6.1.4.1.12559.11.10.1.3.1.42.23 epSOSCodeProb (DYNAMIC)
Tracking / Status = Open 2018-06-05 13:45:36: Tracking by Heiko
Description
Finding:

-

Suggestion:

-

Further explanation:

-

Change Request Status = Closed (lux-gh-issue-42): Add ValueSet for value element
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2018-08-16 12:08:44: Tracking by Samuel
Description
used:
The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.11 epSOSReactionAllergy (DYNAMIC)
or
The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.17 epSOSUnknownInformation (DYNAMIC)
or
The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.5 epSOSIllnessesandDisorders (DYNAMIC)
Tracking / Status = Open 2018-06-05 13:45:49: Tracking by Heiko
Description
Finding:

-

Suggestion:

-

Further explanation:

-

Change Request Status = Open (lux-gh-issue-45): Problem Entry 2nd Template Id
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2018-06-14 14:53:57: Tracking by Heiko
Description
Finding:

- Template should signalize in case of an allergic reaction as a problem

Suggestion:

- Add in that case the templateId @root="2.16.840.1.113883.10.20.1.54"

Template must either signalize a allergic reaction or problem
This may need to be checked within a Schematron rule/Constraint on the level of the Allergies and Intolerances Entry

Further explanation:

-

Change Request Status = Open (lux-gh-issue-52): Usage of effectiveTime high
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2019-01-10 15:28:46: Tracking by Heiko
Description
Finding:

- We need to be clear what listing within this, as the statusCode is foreseen as being in status "completed", means the observation state. We need to be clear with the effectiveTime "High" if it should be present, as by this definition it means that it indicates the time at which the observation was no longer known to be true => so the resolution of the problem. Is it then really relevant to put it into the Résumé Patient?

Suggestion:

-

Further explanation:

-

Change Request Status = Open (lux-gh-issue-53): Participant
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2019-01-10 15:54:21: Tracking by Heiko
Description
Finding:

- Probably exchange by Author structure and review if we shouldn't add more fields like e.g. the functionCode or other id

Suggestion:

-

Further explanation:

-

Change Request Status = Open (lux-gh-issue-62): siteCode ValueSet
TypeChange RequestStatusChange Request Status = Open PriorityNormal
Events
Tracking / Status = Open 2019-07-16 07:26:37: Tracking by Heiko
Description
Finding:

-

Suggestion:

- Assign siteCode valueSet

Further explanation:

-

 
 
Busy
Structure Definitions (External repositories)