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

OK Not OK
Filter
Datasets
Template Associations
Templates
Concept: Patient Data
Idepsos-dataelement-5Version2013-05-31
StatusDraftVersion Label
Description
Information about the patient
/
-
Templates
Name Id Effective date Element or attribute
eHDSI RecordTarget 2.16.840.1.113883.3.1937.777.11.10.100 2013-12-20 hl7:recordTarget
eHDSI RecordTarget 2.16.840.1.113883.3.1937.777.11.10.100 2018-11-14 10:54:53 hl7:recordTarget
eHDSI RecordTarget 2.16.840.1.113883.3.1937.777.11.10.100 2020-04-03 16:17:28 hl7:recordTarget
eHDSI RecordTarget 2.16.840.1.113883.3.1937.777.11.10.100 2020-04-16 10:58:00 hl7:recordTarget
eHDSI RecordTarget 2.16.840.1.113883.3.1937.777.11.10.100 2020-10-02 14:05:45 hl7:recordTarget
eHDSI eDispensation
Issues (2)
Change Request Status = Closed (epsos-issue-362): Relax the constraint for the relatedDocument element
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2021-04-29 12:50:43: Tracking by Mathias Ghys
Description
Implementation done as part of CP-050
Assignment2021-04-29 12:27:33: Assigned To Mathias Ghys by Mathias Ghys
Tracking / Status = Open 2021-04-29 12:27:32: Tracking by Mathias Ghys
Description
Finding:

- The relatedDocument provides a reference to the national version of the document.

The relatedDocument element is currently mandatory. Some MS don't have a national version of the eDispensation message and immediately generate the file to be exchanged. Currently the unique identifier of the document itself is put in the relatedDocument element. It should be made required, so the MS have the choice to put a nullFlavor if not applicable.

Suggestion:

- Modify cardinality/conformance of the relatedDocument element from [1..1] M to [1..1] R.

Further explanation:

- Link to JIRA issue: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-812

Change Request Status = Closed (epsos-issue-363): Limit the @typeCode attribute of the relatedDocument to 'XFRM'
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2021-04-29 12:50:56: Tracking by Mathias Ghys
Description
Implementation done as part of CP-050
Assignment2021-04-29 12:29:38: Assigned To Mathias Ghys by Mathias Ghys
Tracking / Status = Open 2021-04-29 12:29:37: Tracking by Mathias Ghys
Description
Finding:

- Currently, the @typeCode attribute of the relatedDocument is bound to the Act Relationship Type code system, that contains 3 concepts:

  • APND
  • RPLC
  • XFRM

In our case only the concept XFRM can be used (“The current document is a transformation of the ParentDocument”), so it makes sense to set it as a fixed value.


Suggestion:

- Set the @typeCode attribute to a fixed value ('XFRM')

Further explanation:

- Link to JIRA issue: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-341

 
 
Busy