Loading...
Help
Login
Busy
Search
eHDSI - Project Information
 
Warning
Select building block repository
Select user
Select user
Version: Edit
Add/change logo
Remove File
Compare: Releases


Edit
Edit publication parameters

Warning
Edit
Edit
Name
eHDSI
Description

eHDSI in ART-DECOR

About eHDSI

The eHealth Digital Service Infrastructure (eHDSI or eHealth DSI) is the initial deployment and operation of services for cross-border health data exchange under the Connecting Europe Facility (CEF). eHDSI sets up and starts deploying the core and generic services, as defined in the CEF, for Patient Summary and ePrescription. The generic services are the necessary implementation of data exchange at country level, the core services at EU level. These together enable the provision of Cross Border eHealth Information Services (CBeHIS).

History

This project was initially started as the epSOS Large Scale Pilot, where a first version of the CDA implementation guides were created. The transcription to ART-DECOR of the normative master specification for epSOS was originally done by the Dutch National IT Institute for Health Care (Nictiz) end of 2013 / beginning of 2014 as part of an official agreementbetween the epSOS project and Nictiz.The specification as of now is the result of a review of the original epSOS specification. This was done within the EXPAND project WP5, before moving the specification to CEG. The activity was supported by HL7 International /HL7 International Foundation / HL7 Europe. The eHDSI project uses the CDA Implementation Guides of EXPAND asa base for further development.

The CDA IGs of the epSOS project are still available: https://art-decor.org/art-decor/decor-project--epsos-. No active development is done on this project, that served as a base for the eHDSI CDA IGs.

Use cases

Within the eHDSI project, two main use cases are defined:

  • Patient Summary: access to important medical data for patient treatment.
  • ePrescription/eDispensation: cross-border use of electronic prescriptions.

Release notes of the CDA Implementation guides can be found at the following location: https://ec.europa.eu/cefdigital/wiki/x/rYDuAw

The value sets that are used inside the project are combined in a master value set catalogue (MVC): https://ec.europa.eu/cefdigital/wiki/x/yT4ZAg

The Central Terminology Server (CTS) is a set of components used for the representation, access, and maintenance of the terminology content of the electronic documents exchanged within eHealth Digital Service Infrastructure (eHDSI). The CTS aims at supporting the Member States in coordinating their terminology efforts. More information on the CTS can be found in Confluence: https://ec.europa.eu/cefdigital/wiki/x/xz4ZAg

Notes for reading this specification:

  • This specification uses flavors for HL7 V3 datatypes where applicable:
    • AD.EPSOS - checks if there is at least one element if not null
    • CD.EPSOS - allows nested translations, and requires @displayName if @code is used
    • CE.EPSOS / CO.EPSOS / CV.EPSOS - see CD.EPSOS
    • II.EPSOS - OID SHALL be <= 64 characters
    • IVL_TS.EPSOS.TZ / TS.EPSOS.TZ - SHALL be precise to the day, SHALL include a time zone if more precise than to the day, and SHOULD be precise to the second.
    • IVL_TS.EPSOS.TZ.OPT / TS.EPSOS.TZ.OPT - SHALL be precise at least to the year, SHOULD be precise to the day, and MAY omit time zone.
    • TEL.EPSOS - Phone/fax SHALL have pattern '^\+?[0-9()\.-]+$' and SHALL have at least 1 dialing digit
PropertiesPrefix: epsos-Default language: English (en-US)Contains reusable content?The contents of this 'project' are considered suitable for re-use by other projects when this setting is active.Is private?The project is not listed in the menus and ignored in searches when this setting is active. This useful for projects in incubation fase. You may still work in the project based on direct URLsExperimental/Test?Project is experimental or meant to test things rather than aimed at production useNotifier: Determines the project global issue notifier setting (on/off - default is 'on'). Note: changes to this setting are immediately saved.
Publication location
https://art-decor.ehdsi.eu/publication/epSOS/
Project overviewProject Index
Project Id2.16.840.1.113883.3.1937.777.11
Project Last modified2020-08-14 10:00:11
Repository reference
PrefixURLFormat
ad1bbr-http://art-decor.org/decor/services/DECOR
ad2bbr-http://art-decor.org/decor/services/DECOR
RESTful Service
Contributors/Copyright
ContributorTypeLogoCopyright years
epSOS
http://www.epSOS.eu
Author2008-2014
ESNA
Spanish Ministry of Health and Social Politics
Spain
Author2008-2014
LOMBARDY
Regione Lombardia
Italy
Author2008-2014
ELGA
Task Force ELGA and Austrian Ministry of Health
Austria
Author2008-2014
CLM
Regional Health Care Service of Castilla la Mancha
Spain
Author2008-2014
GIPDMP
Group d'intérêt Public-Dossier Médical personnel
France
Author2008-2014
Industry Team
http://www.epsos.eu/home/project-members-beneficiaries/industry-team.html
Team consisting of over 30 companies active in healthcare
Author2008-2014
NICTIZ
National IT Institute for Health Care
The Netherlands
Author2008-2014
NHS
NHS connecting for Health
United Kingdom
Author2008-2014
ZI
Central Research Institute of Ambulatory Health Care
Federal Republic of Germany
Author2008-2014
FHGISST
Fraunhofer Gesellschaft
Germany
Author2008-2014
MEDCOM
Medcom and Danish National Board of Health
Denmark
Author2008-2014
IZIP
IZIP-Internet Access to Patient Electronic Health Record
Czech Republic
Author2008-2014
SALAR
Swedish Associations of Local Authorities and Regions
Sweden
Author2008-2014
NHIC
National Health Information Centre
Slovakia
Author2008-2014
CATA
Fundacio Privada Centre Tic i Salut
Spain
Author2008-2014
DENA
Federal Ministry of Health
Germany
Author2008-2014
Gematik
Germany
Author2008-2014
FRNA
French Ministry of Health
France
Author2008-2014
Authors
NameEmailSubscribe to all issuesEvery author is notified by default for events on issues where he is the author or from the moment he is assigned to an issue. If you would like to keep track of all issue updates, set this to 'on'
Tessa van StijnNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Elze de GrootNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Maarten LigtvoetNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Alexander HenketNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Giorgio CangioliNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Dr. Kai U. HeitmannNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Dr. Stefan SabutschNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Christof GessnerNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Libor SeidlNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Catherine ChronakiNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Marta Terrón CuadradoNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Jérôme SubigerNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Renaud SubigerNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Mathias GhysNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Licínio Kustra ManoNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Yacoubou WaolanyNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Abderrazek BoufahjaNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Hilary RamaNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
adminNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Versions / Releases
Warning



ReadyBusyError
DateByDescriptionStatusPublication
2020-06-17 11:00:53mghysRelease: v4.1.0
There have been changes to the following 3 issues since the last intermediate version or release.
  • Issue 347 "Load new version of the eHDSIActiveIngredient value set based on the MVC v4.1.0 release" with status "Closed". Last event (2020-06-17T10:02:21):
    New value set version loaded.
  • Issue 348 "Load new version of the eHDSIVaccine value set based on the MVC v4.1.0 release" with status "Closed". Last event (2020-06-17T10:00:40):
    New value set version loaded.
  • Issue 349 "Process CDA IG v4.0.0. review remarks" with status "Closed". Last event (2020-06-17T10:00:03):
    Suggested changes implemented.
Under pre-publication review
2020-04-30 15:15:21mghysRelease: v4.0.0
There have been changes to the following 12 issues since the last intermediate version or release.
  • Issue 291 "Bind code element to epSOSAllergenNoDrugs value set and change cardinality" with status "Closed". Last event (2020-04-30T08:12:54):
    Implemented.
    Was already fixed in CDA IG v3.0.0 RC1
  • Issue 297 "Add schematron rule to avoid the schemaLocation attribute to being used" with status "Closed". Last event (2020-04-30T07:43:34):
    Schematron rule added for every document level template and verified.
    Fix already implemented since v3.0.0. RC1
  • Issue 322 "Improve description of hl7:value element" with status "Closed". Last event (2020-04-29T15:35:54):
    Description adapted
  • Issue 338 "Cleanup CDA Template statuses in ART-DECOR" with status "Closed". Last event (2020-04-30T12:19:13):
    Template statuses adapted
  • Issue 339 "Modify languageCode descriptions and Schematron asserts" with status "Closed". Last event (2020-04-30T12:26:59):
    Descriptions adapted.
  • Issue 340 "Element doseQuantity low/high construction not supported" with status "Closed". Last event (2020-04-30T12:47:00):
    Cardinality adapted.
  • Issue 341 "Implement CP-033: Enable indicating dosage period length" with status "Closed". Last event (2020-04-30T12:54:30):
    CP-033 implemented
  • Issue 342 "[Schematron] Validation error for referenced templateId in Problem template" with status "Closed". Last event (2020-04-30T12:59:31):
    Fix implemented
  • Issue 343 "Implement CP-035 Set as mandatory Nature of Patient Summary" with status "Closed". Last event (2020-04-30T13:06:22):
    CP-035 implemented
  • Issue 344 "Implement CP-034: Use of ATC based Value Set for Vaccines" with status "Closed". Last event (2020-04-30T13:09:41):
    Value set eHDSIVaccine loaded in ART-DECOR
  • Issue 345 "Implement CP-032: Include ICD-10 5-character codes" with status "Closed". Last event (2020-04-30T13:25:00):
    Value set eHDSIIllnessandDisorder loaded in ART-DECOR
  • Issue 346 "Implement CP-037: Update project references to eHDSI in CDA IG and MVC" with status "Closed". Last event (2020-04-30T13:42:21):
    references updated
Under pre-publication review
2020-04-06 19:32:44mghysRelease: v3.0.2
There have been changes to the following 14 issues since the last intermediate version or release.
  • Issue 219 "Constraints for custodian organization" with status "Closed". Last event (2020-04-06T13:12:44):
    Fix implemented. We added the hl7:representedCustodianOrganization to the epSOS CDA Custodian template where we could restrict the cardinality of the hl7:telecom element.
    This solution is following the approach taken by the CDA R2 specifications.
  • Issue 225 "custodian org, see epsos-issue-219" with status "Closed". Last event (2020-04-06T13:13:30):
    Fix implemented
  • Issue 227 "custodian org, see epsos-issue-219" with status "Closed". Last event (2020-04-06T13:14:19):
    Fix implemented.
  • Issue 228 "custodian org, see epsos-issue-219" with status "Closed". Last event (2020-04-06T13:14:43):
    Fix implemented.
  • Issue 229 "custodian org, see epsos-issue-219" with status "Closed". Last event (2020-04-06T13:15:08):
    Fix implemented.
  • Issue 230 "custodian org, see epsos-issue-219" with status "Closed". Last event (2020-04-06T13:15:40):
    Fix implemented.
  • Issue 330 "Modify the entry cardinality for the Dispensation section template" with status "Closed". Last event (2020-01-09T11:42:51):
    Fix implemented
  • Issue 331 "Change Code System OID for epSOSIllenssesandDisorders value set" with status "Closed". Last event (2020-04-06T12:12:01):
    Code system OID modified in ART-DECOR
  • Issue 332 "IHE Gazelle EVS client is unable to distinguish between the two different effectiveTime elements (medication regimen and frequency of intakes)" with status "Closed". Last event (2020-04-06T12:08:56):
    Fix implemented for CDA IG v3.0.2. release
  • Issue 333 "IHE Gazelle EVS Client is not able to distinguish between the different hl7:entryRelationship elements with @typeCode='SUBJ'" with status "Closed". Last event (2020-04-06T12:22:19):
    Fix implemented.
  • Issue 334 "Encoding issue when loading value set concepts containing special characters in ART-DECOR" with status "Closed". Last event (2020-04-06T15:10:12):
    Fix implemented.
  • Issue 335 "Replace schematron asserts for hl7:country to textual constraints" with status "Closed". Last event (2020-04-06T17:48:29):
    Fix implemented.
  • Issue 336 "Wrong namespace prefix used in schematron assert for marketingAuthrorizationHolder" with status "Closed". Last event (2020-04-06T13:51:29):
    Prefixes adapted.
  • Issue 337 "Improve description for inFullfillment of element" with status "Closed". Last event (2020-04-06T19:26:45):
    Description improved.
Under pre-publication review
2020-01-06 11:28:48GHYS MathiasRelease: v3.0.1
There have been changes to the following 18 issues since the last intermediate version or release.
  • Issue 134 "No devices example" with status "Closed". Last event (2019-12-23T12:58:27):
    Since Wave 3, we created a confluence page with explicit guidelines on how to handle the cases of known absence/no information of medical devices.
    Code samples were added and using the IPS as an inspiration, examples are added on the level of the template.
  • Issue 171 "multiple instances of effectiveTime" with status "Closed". Last event (2019-12-23T13:37:08):
    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']
  • Issue 231 "participant: duplication of levels " with status "Closed". Last event (2019-12-23T13:43:42):
    Implemented
  • Issue 235 "hl7:assignedPerson contains twice the element hl7:name" with status "Closed". Last event (2019-12-23T13:50:17):
    Ticket can be closed since the containment was removed already in V2.2.0 RC1
  • Issue 295 "Improve description of number of packages element for the substanceAdministration template" with status "Closed". Last event (2019-12-23T14:13:26):
    This issue can be closed since it is implemented based on the non-CP that has been received by support (IM0018146281)
  • Issue 317 "[CP-25] Correct capacityQuantity description after feedback from FI" with status "Closed". Last event (2019-12-04T08:32:27):
    Description adapted
  • Issue 318 "Modify Datatype of effectiveTime element to represent implant data and removal date" with status "Open". Last event (2019-11-07T16:21:43):
  • Issue 319 "Remove binding to obsolete value set epSOSCodeNoMedication " with status "Closed". Last event (2019-11-07T16:21:13):
    Implemented and ready for next release
  • Issue 320 "Providing description for inFulfillmentOf and relatedDocument elements" with status "Closed". Last event (2019-11-11T15:45:05):
  • Issue 321 "Adapt description of hl7:id element" with status "Closed". Last event (2019-11-12T12:11:49):
    Nothing changed. Description was OK. The line from the Change Proposal was not added because of the assessment made by the Semantic Task Force on CP-18
  • Issue 322 "Improve description of hl7:value element" with status "Open". Last event (2019-11-14T16:46:06):
    Finding:

    - Current description is not describing the element correctly:

    Suggestion:

    - We propose: Based on the eHN Guidelines:

    Date on which the woman is due to give birth. Year, month and day are required. If unknown nullFlavor has to be provided.


    Further explanation:

    - Corresponding JIRA issue: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-511

  • Issue 323 "Improve descriptions" with status "Open". Last event (2019-11-19T10:37:34):
    Finding:

    In order to facilitate the life for the implementers, additional documentation must be provided for certain elements in ART-DECOR.

    This Jira issue is to address the most easy ones for which there is currently no description.

    The former EXPAND specifications, the CDA standard and CEN HL7 IPS CDA IGs can serve as inspiration.

    Link to ART-DECOR issue: https://ec.europa.eu/cefdigital/tracker/projects/EHSEMANTIC/issues/EHSEMANTIC-512

    Suggestion:

    - Add descriptions

    Further explanation:

    -

  • Issue 324 "Add typeCode attribute to clinical manifestation" with status "Closed". Last event (2019-11-19T16:25:44):
  • Issue 325 "Add typeCode attribute to severity" with status "Closed". Last event (2019-11-19T16:26:00):
  • Issue 326 "eP Cluster request to modify template description related to prescriptions by overall amount" with status "Closed". Last event (2019-12-10T13:33:17):
    Discription adapted
  • Issue 327 "containment of the general CDA template of a ManufacturedProduct has to be adapted to the epSOS CDA ManufacturedProduct" with status "Closed". Last event (2019-12-23T09:18:57):
  • Issue 328 "Frequency of intakes not bound to the epSOSTimingEvent value set in the case of the EIVL_TS datatype" with status "Closed". Last event (2019-12-23T09:24:25):
    Implemented
  • Issue 329 "Set DataType of ClinicalDocument/id to II" with status "Closed". Last event (2020-01-03T15:01:40):
    Adapted
Under pre-publication review
2019-09-10 07:25:57GHYS MathiasRelease: v3.0.0
There have been changes to the following 7 issues since the last intermediate version or release.
  • Issue 307 "Replace OID in reference to Problem template " with status "Closed". Last event (2019-07-16T07:32:06):
    Implemented
  • Issue 308 "Modify description for strength and package size reflect CP-25" with status "Closed". Last event (2019-07-16T14:24:34):
  • Issue 311 "Link epsos-dataelement-116 only to one element" with status "Closed". Last event (2019-07-16T07:38:09):
    Modified the linking in ART-DECOR
  • Issue 313 "Change MarketingAuthorizationHolder (MAH) subelement namespace prefixes" with status "Closed". Last event (2019-08-28T12:30:47):
    Implemented as a bugfix for the approved change proposal CP-19.
  • Issue 314 "Make patient name element mandatory" with status "Open". Last event (2019-09-03T12:00:20):
    Finding:

    During the gap analysis of the CEN IPS vs eHDSI CDA IGs, it was noticed that the hl7:name element has a conformance of R (required). This allows us to set it to a nullFlavor value. According to  Giorgio CANGIOLI  it is a type and it should be changed to M (mandatory) since the given and family subelements are mandatory and have to be filled in according to the specifications.

    Suggestion:

    - Change conformance from R to M

    Further explanation:

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

  • Issue 315 "CP-31 - Adapt examples to reflect the representation of the strength of medicinal products" with status "Closed". Last event (2019-09-03T15:13:42):
    Implemented and ready to be included in 3.0.0 release
  • Issue 316 "Revert datatype of medical strength from PQ to epsos:PQ" with status "Closed". Last event (2019-09-09T16:17:35):
    Reverted medical strength datatype
Active
2019-07-11 13:55:17GHYS MathiasRelease: v3.0.0 RC2
There have been changes to the following 6 issues since the last intermediate version or release.
  • Issue 307 "Replace OID in reference to Problem template " with status "Open". Last event (2019-05-14T15:19:50):
    Finding:

    - Since the OID of the Problem template has been changed, also the reference to the Problem template has to be adapted with the new OID.
    Link to JIRA issue: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-415

    Suggestion:

    -

    Further explanation:

    -

  • Issue 308 "Modify description for strength and package size reflect CP-25" with status "Open". Last event (2019-05-14T15:31:18):
    Finding:

    - Add descriptions to strength and package size to reflect CP -25
    Link to JIRA issue: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-414

    Suggestion:

    -

    Further explanation:

    -

  • Issue 309 "Add link to "Instructions to patient" data set element" with status "Closed". Last event (2019-06-17T09:44:04):
    Changes applied
  • Issue 310 "Link text element to "Advise to the dispenser" data set element" with status "Closed". Last event (2019-06-17T09:44:23):
    Changes applied
  • Issue 311 "Link epsos-dataelement-116 only to one element" with status "Open". Last event (2019-06-21T09:02:02):
    Finding:

    After an issue I created in the IHE Jira ( https://gazelle.ihe.net/jira/servicedesk/customer/portal/24/DGSANTE-32 ) the conclusion by Kai is the following:

    The element 116 Expected date of Delivery links either to the whole observation (a general approach) or to the hl7:value element, not to the hl7:code element in this case

    The latter is recommended.

    You may link a single data element to different template elements.

    So the data-element linkage can be altered.

    Suggestion:

    - Remove the linkage between epsos-dataelement-116 and hl7:code from the template

    Further explanation:

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

  • Issue 312 "Align description of document level template id elements with IHE ITI Technical framework revision 9" with status "Open". Last event (2019-07-02T16:18:30):
    Finding:

    - At the moment the description is not aligned with the IHE ITI Technical Framework revision 9
    Link with JIRA issue: https://ec.europa.eu/cefdigital/tracker/projects/EHSEMANTIC/issues/EHSEMANTIC-430

    Suggestion:

    -

    Further explanation:

    -

Under pre-publication review
2019-04-30 22:47:37GHYS MathiasRelease: v3.0.0 RC1
There have been changes to the following 76 issues since the last intermediate version or release.
  • Issue 38 "Two different descriptions in the documentation" with status "Closed". Last event (2019-03-21T15:20:39):
    As an outcome from JIRA issue EHSEMANTIC-322, approved by the architecture group, it was confirmed that we can delete the issues related to changes in the Word version of the specifications (which are discontinued)
  • Issue 53 "HP can have only 1 relevant speciality in a given context" with status "Closed". Last event (2019-03-21T15:21:02):
    As an outcome from JIRA issue EHSEMANTIC-322, approved by the architecture group, it was confirmed that we can delete the issues related to changes in the Word version of the specifications (which are discontinued)
  • Issue 55 "Assignement of an epSOS template ID for this section" with status "Closed". Last event (2018-11-19T13:05:42):
    Closed this issue, since I combined all the OID related issues in issue #242: https://art-decor.ehdsi.eu/art-decor/decor-issues-epsos?id=2.16.840.1.113883.3.1937.777.11.6.242

    This is a known issue and has been analyzed on the confluence page: https://ec.europa.eu/cefdigital/wiki/x/haJUAw
  • Issue 58 "Assign an epSOS specific template ID" with status "Closed". Last event (2018-11-19T12:54:31):
    Closed this issue, since I combined all the OID related issues in issue #242: https://art-decor.ehdsi.eu/art-decor/decor-issues-epsos?id=2.16.840.1.113883.3.1937.777.11.6.242

    This is a known issue and has been analyzed on the confluence page: https://ec.europa.eu/cefdigital/wiki/x/haJUAw

  • Issue 64 "Assign an epSOS specific template ID" with status "Closed". Last event (2018-11-19T13:12:43):
    Closed this issue, since I combined all the OID related issues in issue #242: https://art-decor.ehdsi.eu/art-decor/decor-issues-epsos?id=2.16.840.1.113883.3.1937.777.11.6.242

    This is a known issue and has been analyzed on the confluence page: https://ec.europa.eu/cefdigital/wiki/x/haJUAw
  • Issue 90 "check obs.code voc binding" with status "Closed". Last event (2018-11-20T08:58:05):
    This issue can be closed since it is related to the duplicate OID issue which is already listed in issue #242: https://art-decor.ehdsi.eu/art-decor/decor-issues-epsos?id=2.16.840.1.113883.3.1937.777.11.6.242

    The problem is that the Allergies And Intolerances templates should not be a specialization of our Problem template, but of the IHE PCC Problem template, that doesn't have a constraint on the observation/code binding.

    More information can be found on the following confluence page: https://ec.europa.eu/cefdigital/wiki/x/haJUAw
  • Issue 97 "assign an epSOS template ID" with status "Closed". Last event (2018-11-19T13:09:19):
    Closed this issue, since I combined all the OID related issues in issue #242: https://art-decor.ehdsi.eu/art-decor/decor-issues-epsos?id=2.16.840.1.113883.3.1937.777.11.6.242

    This is a known issue and has been analyzed on the confluence page: https://ec.europa.eu/cefdigital/wiki/x/haJUAw
  • Issue 124 "asSpecializedKind missing in Medication Summary Spec" with status "Closed". Last event (2019-03-21T15:21:34):
    As an outcome from JIRA issue EHSEMANTIC-322, approved by the architecture group, it was confirmed that we can delete the issues related to changes in the Word version of the specifications (which are discontinued)
  • Issue 135 "Assign an epSOS specific template" with status "Closed". Last event (2018-11-19T13:07:07):
    Closed this issue, since I combined all the OID related issues in issue #242: https://art-decor.ehdsi.eu/art-decor/decor-issues-epsos?id=2.16.840.1.113883.3.1937.777.11.6.242

    This is a known issue and has been analyzed on the confluence page: https://ec.europa.eu/cefdigital/wiki/x/haJUAw
  • Issue 137 "change oid of the template included for the organizer" with status "Closed". Last event (2018-11-19T13:10:49):
    Closed this issue, since I combined all the OID related issues in issue #242: https://art-decor.ehdsi.eu/art-decor/decor-issues-epsos?id=2.16.840.1.113883.3.1937.777.11.6.242

    This is a known issue and has been analyzed on the confluence page: https://ec.europa.eu/cefdigital/wiki/x/haJUAw
  • Issue 147 "Update document according to CP#08" with status "Closed". Last event (2019-03-21T15:21:52):
    As an outcome from JIRA issue EHSEMANTIC-322, approved by the architecture group, it was confirmed that we can delete the issues related to changes in the Word version of the specifications (which are discontinued)
  • Issue 148 "update specialty cardinality to 0..1" with status "Closed". Last event (2019-03-21T15:22:08):
    As an outcome from JIRA issue EHSEMANTIC-322, approved by the architecture group, it was confirmed that we can delete the issues related to changes in the Word version of the specifications (which are discontinued)
  • Issue 156 "Assert not aligned with the error message" with status "Closed". Last event (2019-04-30T14:24:38):
    Aligned error message with assert.
  • Issue 163 "Check the binding with language VS" with status "Closed". Last event (2018-11-19T16:25:42):
    This issue is a duplicate for issue #182: https://art-decor.ehdsi.eu/art-decor/decor-issues--epsos-?id=2.16.840.1.113883.3.1937.777.11.6.182
    This issue can be closed since we put the constraint to the epsosLanguage value set as done in ticket https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-291

  • Issue 164 "realmCode" with status "Closed". Last event (2018-11-14T09:14:07):
    As agreed in the semantic F2F meeting on 13/11, it was agreed to set the realmCode element to optional for all document level templates.
  • Issue 165 "realmCode" with status "Closed". Last event (2018-11-14T09:13:00):
    As agreed in the semantic F2F meeting on 13/11, it was agreed to set the realmCode element to optional for all document level templates.
  • Issue 166 "realmCode" with status "Closed". Last event (2018-11-14T09:13:44):
    As agreed in the semantic F2F meeting on 13/11, it was agreed to set the realmCode element to optional for all document level templates.
  • Issue 167 "realmCode" with status "Closed". Last event (2018-11-14T09:12:45):
    As agreed in the semantic F2F meeting on 13/11, it was agreed to set the realmCode element to optional for all document level templates.
  • Issue 168 "realmCode" with status "Closed". Last event (2018-11-14T09:13:26):
    As agreed in the semantic F2F meeting on 13/11, it was agreed to set the realmCode element to optional for all document level templates.
  • Issue 169 "classCode, determinerCode" with status "Closed". Last event (2018-11-16T15:47:20):
    Issue can be closed since it has already been implemented in the previous CDA IG releases:
    • v2.1.1
    • v2.2.0
  • Issue 170 "elements in address" with status "Closed". Last event (2018-11-16T13:58:39):
    Closed the issue, as it is was already implemented in the two previous official CDA IG releases:
    • v2.1.1
    • v2.2.0
  • Issue 175 "OID for Comment Template" with status "Closed". Last event (2018-11-19T15:23:04):
    Closed this issue, since I combined all the OID related issues in issue #242: https://art-decor.ehdsi.eu/art-decor/decor-issues-epsos?id=2.16.840.1.113883.3.1937.777.11.6.242  

    This is a known issue and has been analyzed on the confluence page: https://ec.europa.eu/cefdigital/wiki/x/haJUAw
  • Issue 178 "No Entry?" with status "Closed". Last event (2018-11-06T11:20:57):
    Since we don't know what section this issue is about and it's open for more then a year, we decided to close it.
    If Libor specifies which section has to contain the entry definition, we can reopen it...
  • Issue 180 "classCode is mandatory" with status "Closed". Last event (2018-11-06T16:01:36):
    Implemented by Christof Gessner
  • Issue 181 "observation classCode is mandatory" with status "Closed". Last event (2018-11-06T10:49:58):
    Cardinality has been set already to 1...1 and was already defined like this in the previous release, so I guess this issue can be closed
  • Issue 182 "change hl7:languageCode description" with status "Closed". Last event (2018-11-14T13:31:35):
    Constraint added to languageCode element for:
    • document level template
    • recordTarget template
  • Issue 197 "allow for multiple entries" with status "Closed". Last event (2018-11-09T13:58:26):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last two formal releases:
    • V2.1.1
    • V2.2.0
  • Issue 205 "id cardinality" with status "Closed". Last event (2018-11-07T17:07:33):
    I closed this ticket since it's already implemented and available in the latest CDA IG release.
  • Issue 210 "wrong cardinality of section/id" with status "Closed". Last event (2018-11-09T15:03:02):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last two formal releases:
    • V2.1.1
    • V2.2.0
  • Issue 212 "cardinality of manufacturedProduct" with status "Closed". Last event (2018-11-09T15:11:02):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last two formal releases:
    • V2.1.1
    • V2.2.0
  • Issue 215 "effectiveTime maximum multiplicity " with status "Closed". Last event (2018-11-09T15:13:12):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last two formal releases:
    • V2.1.1
    • V2.2.0
  • Issue 216 "text: maximum multiplicity" with status "Closed". Last event (2018-11-07T17:25:14):
    This ticket can be closed, since it has been implemented already and it was part of the latest release.
  • Issue 217 "effectiveTime maximum multiplicity" with status "Closed". Last event (2018-11-09T14:02:07):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last two formal releases:
    • V2.1.1
    • V2.2.0
  • Issue 218 "substanceAdministration maximum multiplicity" with status "Closed". Last event (2018-11-16T15:51:53):
    Issue can be closed since it has already been implemented and it's available in the two previous formal CDA IG releases:
    • v2.1.1 (formal W1 release)
    • v2.2.0 (formal W2 release)
  • Issue 220 "see epsos-issue-219" with status "Cancelled". Last event (2018-11-09T15:14:36):
  • Issue 221 "can not have more than one legalAuthenticator" with status "Closed". Last event (2018-11-20T08:34:54):
    This issue can be closed since it was already adapted and the fix was available in the last two formal releases:
    • v2.1.1
    • v2.2.0
  • Issue 222 "fix cardinality" with status "Closed". Last event (2018-11-20T08:26:38):
    This issue can be closed since the fix has already been implemented and available in the previous two formal releases:
    • v2.1.1
    • v2.2.0
  • Issue 223 "fix cardinality" with status "Closed". Last event (2018-11-16T13:38:26):
    This issue is closed since it has already been fixed in the previous two CDA IG releases:
    • v2.1.1 (official W1 CDA IG release)
    • v2.2.0 (official W2 CDA IG release)
  • Issue 224 "fix cardinality" with status "Closed". Last event (2018-11-09T15:23:03):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last two formal releases:
    • V2.1.1
    • V2.2.0
  • Issue 226 "fix cardinality of status code" with status "Closed". Last event (2018-11-16T13:29:20):
    Closed as it has already been adapted before our two main releases:
    • v2.1.1 (formal Wave 1 release)
    • v2.2.0 (formal Wave 2 release)
  • Issue 232 "participant duplication - see epsos-issue-231" with status "Closed". Last event (2019-04-30T14:15:43):
    Replaced the contains statement by an include statement.
  • Issue 236 "Relaxation of constraints for EntryAllergyAndIntolerance template" with status "Closed". Last event (2018-11-19T10:00:16):
    Change implemented. This is a technical correction, so no need for approval. The Allergies And Intolerances template has to conform to the IHE PCC Problem template. For now this is an issue, since the IHE PCC Problem template and the Problem template use the same OID.

    For the IHE PCC Problem template, the Id has cardinality 1 .. 1 and conformance M
    For the Problem template, the Id has cardinality 1 .. 1 and conformance M

    So it makes sence to also restrict the conformance of the Allergies And Intolerances template to 1 .. 1 M
  • Issue 237 "Create scenario for this template" with status "Closed". Last event (2018-11-29T16:02:33):
    Scenario created and available.
  • Issue 238 "Create scenario for this template" with status "Closed". Last event (2018-11-29T16:02:47):
    Scenario created and available.
  • Issue 241 "inversionInd shall be true" with status "Closed". Last event (2018-11-09T15:52:25):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last formal release:
    V2.2.0
  • Issue 246 "Change cardinality of hl7:languageCode in recordTarget template" with status "Open". Last event (2018-10-12T12:30:48):
    Is not fixed yet...
  • Issue 250 "telecom use code" with status "Closed". Last event (2018-11-09T15:36:20):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last formal release:
    • V2.2.0
  • Issue 251 "telecom nullFlavor value" with status "Closed". Last event (2018-11-09T16:16:17):
    Closed for administrative reasons: fix for this issue was implemented last year and is already present in the last formal release:
    V2.2.0
  • Issue 279 "Fix issue subscription for new ehdsi art décor environment" with status "Open". Last event (2018-08-30T11:52:44):
    Finding:

    - Since the migration of the art décor server from the art-decor infrastructure towards the commission servers, the e-mail notification doesn't work anymore.

    Suggestion:

    -

    Further explanation:

    -

  • Issue 280 "Add templateID to CDA Number of Packages" with status "Cancelled". Last event (2019-03-01T08:35:26):
    Doesn't make sense to add a templateID to this CDA template
  • Issue 281 "Change the cardinality of @classCode and @moodCode to 1 .. 1" with status "Closed". Last event (2018-11-15T14:27:05):
    Implemented after it has been agreed in the semantic F2F meeting (12/13 november)
  • Issue 282 "Make the formCode element of the manufacturedMaterial optional" with status "Closed". Last event (2018-11-19T16:15:20):
    Closed the issue. We proposed the solution of making the manufacturedMaterial optional in the semantic F2F meeting of 12/13 November in Brussels, but although it would technically a solution, it was stressed that the formCode has to be mandatory for the eP/eD documents, but only optional for the PS documents.

    Since this requirement cannot be fulfilled using a common template, 2 separate templates have to be created as a specialization of the current one. But this changes the specifications and has to occur through a change proposal.
    This issue is a duplicate of the older one: https://art-decor.ehdsi.eu/art-decor/decor-issues--epsos-?id=2.16.840.1.113883.3.1937.777.11.6.126 so it was decided to close this one and to keep the old one.
  • Issue 283 "Remove determinerCode from epsos:ingredient element" with status "Closed". Last event (2018-11-15T14:31:31):
    Implemented after it has been agreed in the semantic F2F meeting (12/13 november)
  • Issue 284 "Remove constraint that @unit value has to come from UCUM value set for capacityQuantity" with status "Closed". Last event (2018-11-20T08:49:32):
    Constraint removed after approval by the semantic group during the semantic F2F meeting in Brussels on the 12/13th of November 2018.
    Added a textual constraint.
  • Issue 285 "Add description to epsos:asContent/epsos:name element" with status "Closed". Last event (2019-04-30T14:30:18):
    Descriptions approved during eP cluster meeting and added to the CDA IGs
  • Issue 286 "modify example and change observation attribute from typeCode -> classCode" with status "Closed". Last event (2018-09-20T13:32:06):
    Corrected example
  • Issue 287 "Unknown datatype used for ingredient numerator/denumerator" with status "Deferred". Last event (2018-11-09T15:11:32):
    reply from Giorgio:
    epsos:PQ is identical to PQ. It is just a consequence of the way the XSD was built at the time of epSOS.
    I suggest to create a CP to move from the epSOS:dtataype to the standard datatype , this implies you need to generate new schema with extension.

    We cannot simply change it at the moment, since this implies that the CDA extended XSD scheme has to be adapted, since it expects the epsos:PQ datatype at the moment.
  • Issue 288 "Set OpenMed ManufacturedProduct template status to retired" with status "Closed". Last event (2018-11-14T08:43:57):

    In the semantic F2F meeting on 13/11, it was agreed upon to change the template status of the two templates to 'retired'. Like this we don't lose them and they are still there, but they are filtered out in the overview.

    If we don't receive any feedback to reactivate them in the coming 2 years, we can delete them.

  • Issue 289 "Set OpenMed Material template status to retired" with status "Closed". Last event (2018-11-14T08:44:29):

    In the semantic F2F meeting on 13/11, it was agreed upon to change the template status of the two templates to 'retired'. Like this we don't lose them and they are still there, but they are filtered out in the overview.

    If we don't receive any feedback to reactivate them in the coming 2 years, we can delete them.

  • Issue 290 "Add MarketingAuthorizationHolder element" with status "Closed". Last event (2018-11-16T12:49:29):
    This element is implemented in ART-DECOR.
    It will be presented to the eP cluster and available in the next CDA IG release.
  • Issue 291 "Bind code element to epSOSAllergenNoDrugs value set and change cardinality" with status "Open". Last event (2018-12-05T16:32:50):
    Finding:

    We noticed there is no binding in the CDA IG to the epSOSAllergenNoDrugs value set.

    Within the Allergies And Intolerances section, we have the participant that is the allergen - the substance that caused the allergy.

    Within the CDA template, this info can be found in the participantRole/participantEntity code element

    Suggestion:

    - Add the binding and modify the cardinality/conformance to 1 .. 1 /R

    Further explanation:

    -

  • Issue 292 "Prescriber issue in substanceAdministration template - need for clarification" with status "Closed". Last event (2019-04-30T14:17:22):
    Created Dispenser Credentialing Organization template.
  • Issue 293 "Schematron validation error for CDA Organization address" with status "Closed". Last event (2019-04-30T14:22:09):
    Schematron rule adapted and corrected.
  • Issue 294 "Improve description for hl7:assignedAuthor/hl7:id" with status "Closed". Last event (2019-04-30T14:28:18):
    Description adapted
  • Issue 295 "Improve description of number of packages element for the substanceAdministration template" with status "Open". Last event (2019-02-15T13:51:34):
    Finding:

    - A lot of confusion about this element in the preparation of the February test event.

    An issue has been created in JIRA: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-381

    Suggestion:

    Comment proposed by   Konstantin HYPPÖNEN

    The description of field Number of Packages is the following: The supply entry should indicate the quantity supplied (such as tablets or containers). The value attribute shall be present and indicates the quantity of medication supplied. If the medication is supplied in dosing units (tablets or capsules), then the unit attribute need not be present (and should be set to 1 if present). Otherwise, the unit element shall be present to indicate the quantity (e.g., volume or mass) of medication supplied.

    feedback from Christof GESSNER  absent information means "1"

    Further explanation:

    -

  • Issue 296 "[Allergy Cause]Bind Allergy cause to value sets" with status "Cancelled". Last event (2019-03-01T16:28:32):
    Is duplicated by https://art-decor.ehdsi.eu/art-decor/decor-issues--epsos-?id=2.16.840.1.113883.3.1937.777.11.6.291
  • Issue 297 "Add schematron rule to avoid the schemaLocation attribute to being used" with status "Open". Last event (2019-02-25T09:50:49):
    Finding:

    - From the CDA book:

    Do Not Use the schemaLocation Attribute


    While the XML Schema Language allows a schema location to be associated with an XML

    document by including a schemaLocation attribute associated with the http://www.

    w3.org/2001/XMLSchema-instance namespace, this is explicitly PROHIBITED

    by [ITS§1.4], and thus by the CDA standard.

    Systems validating a CDA document are expected to provide their own schemas to use

    during validation. This rule is sometimes broken by CDA implementers. Applications

    receiving CDA documents should at the very least REMOVE the schemaLocation

    attribute

    from the document before processing it, if not rejecting documents containing

    them completely. Downloading schema resources from arbitrary URLs or file locations for

    validation can at the very least slow down your system, and could crash it or even worse,

    cause a security breach. I have seen a number of different systems crash at testing events

    upon seeing an otherwise valid CDA document containing a schemaLocation attribute

    pointing to a file that does not exist.

    Suggestion:

    - Add a schematron rule to avoid the use of the schemaLocation attribute. Has to be added to every CDA Document Level Template.
    JIRA issue has been created for this: https://ec.europa.eu/cefdigital/tracker/browse/EHSEMANTIC-385

    Further explanation:

    -

  • Issue 298 "Fix templateID OID that is reusing the one from the IHE PCC" with status "Closed". Last event (2019-04-30T14:12:31):
    Created new template with new OID
  • Issue 299 "Consider the removal of the CDA Number of Packages template" with status "Closed". Last event (2019-04-30T14:29:21):
    Template removed and content migrated into epSOS CDA substanceAdministration template
  • Issue 300 "Align the CDA IGs with the guidelines on representation of "known absence" and "no information" for the required sections and link with the newly created value sets." with status "Closed". Last event (2019-04-30T13:52:27):
    Aligned with guidelines on representation of "known absence" and "no information" for the required sections .
  • Issue 301 "Remove CD.EPSOS datatype from epsos:ingredient element" with status "Closed". Last event (2019-04-30T14:31:07):
    Removed ingredient data type
  • Issue 302 "Changing medical strength datatype from epsos:PQ to PQ" with status "Closed". Last event (2019-04-30T14:13:04):
    Datatypes adapted
  • Issue 303 "Add consumable element to align Related Prescription Item with XSD schema definitions" with status "Closed". Last event (2019-04-30T14:17:59):
    Added consumable element to Related Prescription Item template.
  • Issue 304 "Change example: replace typeCode by classCode" with status "Closed". Last event (2019-04-30T13:20:06):
    Example adapted
  • Issue 305 "Remove epSOSUnits binding in epsos:capacityQuantity/@unit attribute" with status "Closed". Last event (2019-04-30T13:24:44):
    Removed the value set constraint
  • Issue 306 "Review the value set binding of the value element within the Problem template" with status "Closed". Last event (2019-04-30T14:31:31):
    Review finished
Under pre-publication review
2018-08-16 12:56:36GHYS MathiasRelease: v2.2.0
There have been changes to the following 10 issues since the last intermediate version or release.
  • Issue 240 "moodCode shall be INT" with status "Closed". Last event (2018-07-17T08:10:54):
    I guess this issue can be closed since the moodCode is adapted in ART-DECOR.
    I agree with the proposal.
  • Issue 275 "Change the Cardinality of the id and text elements according to the IHE PCC" with status "Feedback needed". Last event (2018-06-11T10:24:17):
    Dear Giorgio, thank you for your feedback. This is highly appreciated.

    I always create tickets for the things I want to change where I don't feel 100% confident, and ask for feedback from the semantic experts. 
    This is one of these cases. I changed the issue status to "Feedback needed" and Label "(TBA) To be approved".

    If I understand it correctly, we make the following distinction:

    • specialization: we modify an existing template (in this case the IHE PCC template) and add some self-defined elements or we add some additional restrictions to existing elements (as been decided in previous project phases)
    • adaptation: we use an existing template as a base but add/modify elements so that the template is not following the rules of the original template anymore.
    From the definition of the templateId: "Use of the templateId indicates that the CDA instance conforms to the constraints specified by each templateId referenced as well as to the standard CDA schema" (Principles of Health Interoperability)

    As you mentioned, I also noticed the fact that in a lot of cases the templateId is specified, even when the template is not conform to the constraints specified by the referenced template.

    I think there are 2 problems that have to be fixed:
    1. Some eHDSI reuse the exisiting OID from the IHE PCC templates. This is just wrong. The templates should receive eHDSI specific template IDs.
    2. In my opinion, no template IDs can be specified if the template is not a specialization of the template. The fact if a template is an adaptation/specialization is described in the description.
    I don't see a problem in just removing the template IDs in the case of an adaptation, since validation won't fail the CDA document if the template ID is still mentioned, but in that case, at least the templates are correctly described. Another option is to just make them conform to the referenced templates, but I don't think this is the way to go, since in this case we are reverting changes that have been made in previous project phases (like the choice you mentioned where the choice of epSOS was not to impose that entries would be linked to the section text)

    What do you think?
  • Issue 276 "make patient name mandatory (change conformance from R to M)" with status "Open". Last event (2018-06-21T12:59:25):
    Finding:

    From the functional requirements, the family/first name of a patient is mandatory. But if in ART-DECOR the parent element (name) allows a nullFlavor, there is the possibility to have a valid CDA document without providing the family/first name of a patient.

    Suggestion:

    - Change the conformance from R to M

    Further explanation:

    -

  • Issue 277 "Restrict the nullFlavor value for Telecom element in author to "NI"" with status "Open". Last event (2018-06-21T13:10:10):
    Finding:

    For reasons of consistency with other telecom elements, restrict the nullFlavor value of the assignedAuthor element to "NI". It is also specified like this in the Expand documentation.

    Suggestion:

    - Restrict nullFlavor value of assignedAuthor to "NI"

    Further explanation:

    -

  • Issue 278 "Restrict the nullFlavor value for Telecom element in author prescriber to "NI"" with status "Open". Last event (2018-06-21T13:16:02):
    Finding:

    For reasons of consistency with other telecom elements, restrict the nullFlavor value of the assignedAuthor element to "NI". It is also specified like this in the Expand documentation.

    Suggestion:

    - Restrict nullFlavor value of assignedAuthor to "NI"

    Further explanation:

    -

  • Issue 279 "Fix issue subscription for new ehdsi art décor environment" with status "Open". Last event (2018-06-26T13:33:32):
    Finding:

    - Since the migration of the art décor server from the art-decor infrastructure towards the commission servers, the e-mail notification doesn't work anymore.

    Suggestion:

    -

    Further explanation:

    -

  • Issue 280 "Add templateID to CDA Number of Packages" with status "Open". Last event (2018-07-03T12:50:48):
    Finding:

    - At this moment, the CDA NumberOfPackages template has an epSOS OID and was created for reuse. However, this template doesn't have a templateID

    Suggestion:

    - At the templateID for this template

    Further explanation:

    -

  • Issue 281 "Change the cardinality of @classCode and @moodCode to 1 .. 1" with status "Open". Last event (2018-07-18T08:03:41):
    Finding:

    - We noticed that, although ART-DECOR states that the attributes are optional, the XSD states that it's mandatory. 
    The schema error is correct, as the attribute is required as per W3C schema (and that makes sense for the classCode).
    Therefore you MUST specify this in the template as 1..1, either fixed or with a value set of valid class codes.

    Suggestion:

    - Change the cardinality from 0 .. 1 to 1 .. 1

    Further explanation:

    -

  • Issue 282 "Make the formCode element of the manufacturedMaterial optional" with status "Open". Last event (2018-07-26T15:24:55):
    Finding:

    - From the discussion with dr. Christof Gessner: If we look into the expand documentation, we noticed that the formCode has to have cardinality 1 .. 1 and conformance R for ePrescription and eDispensation. However, for PatientSummary, the formCode has to have cardinality 0 .. 1 and be optional. Since this template is reused in all document templates (eP, eD, PS) we should make the element optional.
    This won't have any impact on the document validation, since eP/eD messages will still be valid (there is just the relaxation of the constraint)

    Suggestion:

    - Make the element optional.

    Further explanation:

    -

  • Issue 283 "Remove determinerCode from epsos:ingredient element" with status "Open". Last event (2018-08-07T07:48:31):
    Finding:

    - In ART-DECOR, we have two attribute values defined for the upper epsos:ingredient element: @classCode and @determinerCode with both fixed values. But when we add these attributes as defined in ART-DECOR, we have XSD schema validation errors. The @determinerCode should be removed from ART-DECOR (this is also in line with the EXPAND documentation)

    Suggestion:

    - Remove the @determinerCode attribute with it's fixed value from the epsos:ingredient element

    Further explanation:

    -

Active
2018-06-08 11:29:58Mathias GhysRelease: v2.2.0 RC4
There have been changes to the following 6 issues since the last intermediate version or release.
  • Issue 270 "Adapt form code example to contain the new OID for the EDQM code system" with status "Closed". Last event (2018-05-18T09:30:16):
    modified the example and the erroneous namespace prefix was fixed by dr Kai Heitmann
  • Issue 271 "Implement changes related to Approved CP-018" with status "Closed". Last event (2018-05-18T12:18:18):
    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.



  • Issue 272 "restrict formCode CONF to epSOSPackage value set for asContent part" with status "Open". Last event (2018-05-25T11:52:02):
    Finding:

    - In the asContent element we see the following description:
    This structure describes the packaging of the medication. The element provides the code for the particular package.

    But if we go into the formCode, we have the freedom to choose from the epSOSDoseForm value set OR the epSOSPackage value set. In my opinion, the Pharmaceutical dose form has to come into the formCode element under the manufacturedMaterial level and the formCode element under the /asContent/containerPackageMedicine can only contain values from the epSOSPackage value set

    Suggestion:

    - Remove the possibility to have a value from the 2 value sets.

    Further explanation:

    -

  • Issue 273 "For reasons of clarity, every Social History Observation should have an id and " with status "Closed". Last event (2018-06-08T11:21:17):
    id and text element are added to comply with the Simple Observation Template
  • Issue 274 "Change cardinality of value element" with status "Open". Last event (2018-06-08T10:54:16):
    Finding:

    - We received a question from Heiko Zimmermann:
    The "value" element, shouldn't it be with a cardinality 1..1 instead of 0..* ? as it is mentioned that it  shall  be given. Is a max "*" cardinality really useful in practice?

    I had a look in the IHE PCC templates:
    https://art-decor.ihe-europe.net/art-decor/decor-templates--IHE-PCC-?id=1.3.6.1.4.1.19376.1.5.3.1.4.6

    In this template the cardinality of the value element is 1 … *:

    I don't know if these this template is something official we can rely on (I guess it's based on this pdf document: http://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_TF_Vol2.pdf  since the ART-DÉCOR references the paragraph in this document)?

    From the pdf document:

    6.3.4.15.5 <value xsi:type='CD' code=' ' codeSystem=' ' codeSystemName=' ' displayName=' '>

    The <value> is a description of the allergy or adverse reaction. While the value may be a coded or an uncoded string, the type is always a coded value (xsi:type='CD'). If coded, the code and codeSystem attributes must be present. The codingSystem should reference a controlled vocabulary describing allergies and adverse reactions, see Table 5.4 12 above. If uncoded, all attributes other than xsi:type='CD' must be absent. The allergy or intolerance may not be known, 5570 in which case that fact shall be recorded appropriately. This might occur in the case where a patient experiences an allergic reaction to an unknown substance.

    In the pdf we don't have any indication about the cardinality.

    BUT, if the IHE PCC has a minimum cardinality of 1 and our template has a minimum cardinality of 0, it means we are not compatible with the IHE PCC templates, since omitting the value will provide a valid document according to the ehDSI specifications, but will be an invalid document according to the IHE PCC templates.

    Suggestion:

    - Change the cardinality from 0 ... * to 1 ... 1 or at least 0 ... 1

    Further explanation:

    -

  • Issue 275 "Change the Cardinality of the id and text elements according to the IHE PCC" with status "Open". Last event (2018-06-08T11:03:45):
    Finding:

    This template is a subtype of the Problem Entry, and so must also confirm to the rules of the problem entry, which has the template identifier of 1.3.6.1.4.1.19376.1.5.3.1.4.5. This is an OID from the IHE PCC that is duplicated by an eHDSI template. But from the description, I understand that the templateId is referring to the IHE PCC Problem Entry. There the hl7:id and hl7:text are 1 … 1 M. Then I don't see why the hl7:id and hl7:text are 0 … * R and 1 … 1 R .

    Suggestion:

    - Lets make this template compatible with the IHE PCC Problem template and change the cardinality and conformance

    Further explanation:

    -

Under pre-publication review
2018-05-04 10:04:48Mathias GhysRelease: v2.2.0 RC3
There have been changes to the following issue since the last intermediate version or release.
  • Issue 269 "Restrict the cardinality on the entries of a Prescription" with status "Closed". Last event (2018-05-04T09:59:19):
    I adapted the cardinality.
Under pre-publication review
2018-04-10 17:18:58Mathias GhysRelease: v2.2.0 RC2
There have been changes to the following 13 issues since the last intermediate version or release.
  • Issue 255 "country element in addr has to come from the epSOS country value set if available" with status "Feedback needed". Last event (2018-01-11T16:53:34):
    Dear Giorgio,

    Thank you for the feedback. Very well appreciated. But could you provide me some clarification?
    To give you a little context on why I did this change:
    IHE Europe creates validators based on our ART-DECOR implementation guides. Before the validator was based on the paper specifications in EXPAND.
    To identify the differences in validation results between the old validator and the new ART-DECOR based one, a gap analysis was done between the two:
    For the Country, there was this difference that the old validator checked that the value in the country element was coming from the epsosCountry value set.
    In ART-DECOR there was no rule for this.
    hl7:addr is of datatype AD.EPSOS and country is a subelement with datatype ADXP. I wanted to indicate that the value of the country subelement has to come from the epsosCountry value set.
    So that <country>IT</country> is allowed and not <country>ITALY</country>

    What is the correct way to define this in ART-DECOR?


  • Issue 257 "added the templateId element" with status "Closed". Last event (2018-01-11T18:49:18):
    Finding:

    - added the templateId element

    Suggestion:

    -

    Further explanation:

    -

  • Issue 258 "Remove lock from template" with status "Closed". Last event (2018-01-12T09:37:36):
    Finding:

    - Can't edit template. Error message says: Template locked User Oliver Egger 2017-11-27

    Suggestion:

    -

    Further explanation:

    -

  • Issue 259 "No conformance set for ActiveIngredient substance name" with status "Open". Last event (2018-04-05T11:51:38):
    In the EXPAND PDF Spec this corresponds to R4.3, saying that this element is optional. As the  datatype is ST, using nullFlavor is not an option. However, in the code element you also have the name.
  • Issue 260 "Change participant constraint text: replace inactive concept" with status "Closed". Last event (2018-02-12T15:13:03):
    Text adapted
  • Issue 261 "Add effectiveTime to EntryVitalSignsObservatoin" with status "Cancelled". Last event (2018-03-02T10:57:06):
    Duplicate of issue 263
  • Issue 262 "Adapt examples according to specification" with status "Closed". Last event (2018-03-14T16:18:31):
    We received the confirmation in the semantic group in the meeting of 14/3 to change the moodCode attribute and it has been adapted.
  • Issue 263 "Add effective time element to Vital Signs Observation" with status "Closed". Last event (2018-03-28T11:07:56):
    Effective type with datatype TS has been added to the Vital Signs Observation template.
    Issue is related to issue #266
  • Issue 264 "Add effective time element to Social History Observation" with status "Closed". Last event (2018-03-26T17:19:16):
    This topic was discussed at the Semantic WG tcon on 26/3/2018 and this is what has been decided:
    In the CDA IGs: we restrict the effectiveTime to onlyan interval (through the low/high subelements) and we don't allow a specific timestamp (through the value attribute) anymore. We improved the description and hope it will be more clear and less confusing.
    Clinically it is meaningful, since it doesn't make sense to specify a single day for smoking behaviour or alcohol consumption.
    As a consequence, we only have to foresee the display of the low/high subelements in the CDA Display tool.
  • Issue 265 "Add templateID 2.16.840.1.113883.10.20.1.54 to manifestation observation." with status "Rejected". Last event (2018-03-28T11:02:57):
    It was agreed upon to remove the dependency to the CCD template (2.16.840.1.113883.10.20.1.54) from the allergies observation. No formal reason could be found to keep it. Since the constraint was just in textual form, it won't be tested in the validation.

    It's a spurious remaining from the IHE PCC, where conformance to CCD was requested. No formal rules could be seen that could not be covered by other templates present in the Allergy Reaction Observation.


  • Issue 266 "Change the datatype of the effectiveTime for the Vital Signs Organizer from IVL_TS to TS" with status "Closed". Last event (2018-03-28T10:55:06):
    Datatype is changed from IVL_TS to TS.
    This has been agreed upon in the working session with the eHDSI solution provider. I also extended the description and added an example for clarification.
  • Issue 267 "Remove the textual constraint to the CCD template for the Allergies reaction observation" with status "Closed". Last event (2018-03-28T10:52:56):
    Textual constraint removed from the template.
    I also removed it from the example in the observation for the immunizations. Since there it was not in the description, but only in the example and this is very confusing.
  • Issue 268 "Restrict effective Time in the entries of the Medical Devices Section" with status "Closed". Last event (2018-04-05T12:02:55):
    Changed the datatype for the effectiveTime in the Medical Devices Template from IVL_TS to TS and adapted the description accordingly.
Under pre-publication review
2018-01-10 17:19:30Mathias GhysRelease: V2.2.0 RC1
There have been changes to the following 20 issues since the last intermediate version or release.
  • Issue 237 "Create scenario for this template" with status "Open". Last event (2017-11-20T18:27:02):
    In order to make ART-DECOR create the Schematron files
  • Issue 238 "Create scenario for this template" with status "Open". Last event (2017-11-20T18:27:29):
    In order to make ART-DECOR create the Schematron files
  • Issue 239 "Modify effectiveTime element for Medical Device template" with status "Feedback needed". Last event (2017-11-23T20:51:26):
    If we want the schematrons as intended, people _have_ to stick to the "usual" namespace prefixes like...epsos

    That is what Implementation Guides typically do, e.g. see IHE
  • Issue 240 "moodCode shall be INT" with status "In Progress". Last event (2017-11-24T13:36:16):
    Finding:

    -

    There is an inconsistency between the specification with OID 1.3.6.1.4.1.19376.1.5.3.1.4.3.1 in the older EXPAND documentation (where the implementation guides were written in paper) where the old validator was based upon and the current ART-DÉCOR definitions.

    Suggestion:

    - Change to moodCode=INT

    Further explanation:

    - I checked the PDF documentation, the parent template from IHE PCC 1.3.6.1.4.1.19376.1.5.3.1.4.3.1, and the C-CDA template 2.16.840.1.113883.10.20.1.43

    (see https://art-decor.ihe-europe.net/art-decor/decor-templates--IHE-PCC-?id=1.3.6.1.4.1.19376.1.5.3.1.4.3.1 )

    Also see IHE PCC TF2  6.3.4.8.4:
     <act  classCode='ACT' moodCode='INT'>
    The  related  statement   is  the  intent   (moodCode='INT')  on  how  the  related  entry  is  to  be 
    performed.


  • Issue 241 "inversionInd shall be true" with status "In Progress". Last event (2017-11-24T13:59:48):
    Finding:

    - no fixed value for inversion Ind

    Suggestion:

    - fixed inversionInd value true, according to IHE PCC 1.3.6.1.4.1.19376.1.5.3.1.4.7, and epsos PDF specification

    Further explanation:

    -

  • Issue 242 "Fix duplicate OIDs in ART-DECOR" with status "Open". Last event (2017-11-29T12:39:09):
    Finding:

    We noticed that the same OIDs are used in ART-DECOR for defining different templates. This originates from the older implementation guide definitions in the EXPAND period and is a known issue for some time.
    The majority of conflicts arises from re-using templates from IHE PCC in epSOS, but with additional constraints.
    I compared the list of templates in epsos: http://art-decor.org/art-decor/decor-template-ids--epsos-
    with the IHE PCC templates: https://art-decor.ihe-europe.net/art-decor/decor-template-ids--IHE-PCC-

    I tried to list the templates where the OID is reused in epSOS:

    • 1.3.6.1.4.1.19376.1.5.3.1.1.5.3.2 - Section Coded Vital Signs
    • 1.3.6.1.4.1.19376.1.5.3.1.1.5.3.4 - Section Pregnancy History
    • 1.3.6.1.4.1.19376.1.5.3.1.1.9.50 - Section Health Maintenance Care Plan
    • 1.3.6.1.4.1.19376.1.5.3.1.3.6 - Section Active Problems
    • 1.3.6.1.4.1.19376.1.5.3.1.3.8 - Section History of Past Illness
    • 1.3.6.1.4.1.19376.1.5.3.1.3.12 - Section Coded List of Surgeries
    • 1.3.6.1.4.1.19376.1.5.3.1.3.13 - Section Allergies and Other Adverse Reactions
    • 1.3.6.1.4.1.19376.1.5.3.1.3.16.1 - Section Coded Social History
    • 1.3.6.1.4.1.19376.1.5.3.1.3.17 - Section Functional Status
    • 1.3.6.1.4.1.19376.1.5.3.1.3.23 - Section Immunizations
    • 1.3.6.1.4.1.19376.1.5.3.1.4.1 - Severity
    • 1.3.6.1.4.1.19376.1.5.3.1.4.1.1 - Entry Problem Status Observation
    • 1.3.6.1.4.1.19376.1.5.3.1.4.1.2 - Entry Health Status Observation
    • 1.3.6.1.4.1.19376.1.5.3.1.4.2 - Comment
    • 1.3.6.1.4.1.19376.1.5.3.1.4.3 - epSOS Patient Medication Instructions
    • 1.3.6.1.4.1.19376.1.5.3.1.4.3.1 - Entry Medication FulFillment Instructions
    • 1.3.6.1.4.1.19376.1.5.3.1.4.4 - External Reference
    • 1.3.6.1.4.1.19376.1.5.3.1.4.4.1 - Internal Reference
    • 1.3.6.1.4.1.19376.1.5.3.1.4.5 - Problem
    • 1.3.6.1.4.1.19376.1.5.3.1.4.5.2 - Problem Concern
    • 1.3.6.1.4.1.19376.1.5.3.1.4.5.3 - Allergy and Intolerance Concern
    • 1.3.6.1.4.1.19376.1.5.3.1.4.6 - Allergies And Intolerances
    • 1.3.6.1.4.1.19376.1.5.3.1.4.7.2 - Immunization Product
    • 1.3.6.1.4.1.19376.1.5.3.1.4.12 - Immunizations
    • 1.3.6.1.4.1.19376.1.5.3.1.4.13 - Simple Observation
    • 1.3.6.1.4.1.19376.1.5.3.1.4.13.1 - Vital Signs Organizer
    • 1.3.6.1.4.1.19376.1.5.3.1.4.13.2 - Vital Signs Observation
    • 1.3.6.1.4.1.19376.1.5.3.1.4.13.4 - Social History Observation
    • 1.3.6.1.4.1.19376.1.5.3.1.4.13.5 - Pregnancy Observation
    • 1.3.6.1.4.1.19376.1.5.3.1.4.13.6 - Blood Group
    • 1.3.6.1.4.1.19376.1.5.3.1.4.19 - Procedure
    Suggestion:

    Change the OIDs. To what OIDs has to be discussed and maybe the change has to occur by a change request.

    Further explanation:

    -

  • Issue 243 "Description of epsos:Ingredient is wrong" with status "Closed". Last event (2017-12-07T19:16:16):
    Closed after having verified the solution with Konstantin Hyppönen.
  • Issue 244 "Fixed value for nullFlavor is inconsistent with description and former EXPAND documentation" with status "Closed". Last event (2017-12-06T10:43:08):
    • Conformance of Organisation changed from 1 ... 1 M to 1 ... 1 R
    • nullFlavor fixed value for telecom element changed from 'UNK' to 'NI'

  • Issue 245 "Relax the constraint that the hl7:code shall be from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.23 epSOSCodeProb (DYNAMIC)" with status "Closed". Last event (2017-12-08T17:09:24):
    Just from a ART-DECOR definitional and validator perspective:

    There are two, and after an intermediate release next week four, vocab binding strengths:
    Coded no exceptions = Required => violation will always throw an error. CNE is the default, i.e. if none is specified, CNE is assumed.
    Coded with exceptions = extensible => violation will always throw an info
    Preferred => violation will always throw an info
    Example => violation will always throw an info

    Hope this helps.
  • Issue 246 "Change cardinality of hl7:languageCode in recordTarget template" with status "Closed". Last event (2017-12-08T12:19:27):
  • Issue 247 "Missing elements in epSOS CDA substanceAdministration template" with status "Open". Last event (2017-12-15T17:09:12):
    Finding:

    - Some previously available constructs are missing:

    • Number of packages
    • Patient instructions
    In the epSOS CDA IGs in ART/DECOR (comparison document) we find the following:

    • Add the required element R4.8, Number of packages (Number of Packages) ( entry/substanceAdministration[templateId/[@root='1.3.6.1.4.1.12559.11.10.1.3.1.3.2']/entryRelationship[@typeCode='COMP']/ supply[@moodCode= 'RQO' and independentInd/@value='false']/quantity)
    This is indicated as "ALL DONE"

    Nothing is set in this document about the patient Instructions


    Suggestion:

    -

    Further explanation:

    -

  • Issue 248 "hl7:name cardinality must be changed from 0 ... 1 to 1 ... 1" with status "Open". Last event (2017-12-18T10:50:39):
    Finding:  

    - outcome of gap analysis of Abderrazek: consumable/manufacturedProduct/manufacturedMaterial/name required. In Expand the Cardinality is for the element is: (eP/eD/PS: R/NA/NA).

    Suggestion:

    - Change the cardinality from 0 ... 1 to 1 ... 1

    Further explanation:

    -

  • Issue 249 "Set Telecom element in line with usages in other templates" with status "Closed". Last event (2018-01-05T16:58:21):
    Fixed the Telecom element, but I didn't create a separate Template yet...
  • Issue 250 "telecom use code" with status "Open". Last event (2018-01-08T11:46:08):
    Finding:

    - telecom @use is required, but should be optional, according to text.

    Suggestion:

    - change cardinality to 0...1 (as in other occurences of telecom)

    Further explanation:

    -

  • Issue 251 "telecom nullFlavor value" with status "Open". Last event (2018-01-08T11:52:44):
    Finding:

    - to be changed from UNK to NI

    Suggestion:

    -

    Further explanation:

    -

  • Issue 252 "Add nullFlavor possibility with NI fixed value to Telecom element" with status "Closed". Last event (2018-01-08T17:19:23):
  • Issue 253 "Adapt conformancy of family and given elements conform the EXPAND specifications" with status "Feedback needed". Last event (2018-01-09T12:38:14):
    OK. I removed the contain statement.

    Note that the intention to make those fields mandatory will fail if not all enclosing elements are also mandatory. Otherwise, the sender can just use a nullFlavor on one of the enclosing levels.
  • Issue 254 "Adapt Telecom element with relation to other elements" with status "Closed". Last event (2018-01-10T09:38:56):
    Changed according to requirement R1.10.8 in the EXPAND documentation
  • Issue 255 "country element in addr has to come from the epSOS country value set if available" with status "Closed". Last event (2018-01-10T16:19:27):
    Added the constraint
  • Issue 256 "Change Conformance of HCP assignedPerson family and given name according to documentation" with status "Closed". Last event (2018-01-10T16:15:35):
    I processed the changes
Draft
2017-11-17 11:09:31Mathias GhysRelease: V2.1.1
There have been changes to the following 200 issues since the last intermediate version or release.
  • Issue 2 "Add laparoscopic colectomy" with status "Open". Last event (2016-03-29T13:36:09):
    To be considered for Next MVC version
  • Issue 24 "Value set epSOSCodeProb without dataset binding" with status "Closed". Last event (2016-03-17T17:46:53):
  • Issue 31 "Value set epSOSPersonalRelationship without dataset binding" with status "Closed". Last event (2016-03-17T17:53:46):
    Modified the binding for the /ClinicalDocument/participant/associatedEntity/code 
  • Issue 32 "Value set epSOSRoleClass without dataset binding" with status "Closed". Last event (2016-03-17T17:59:20):
    this value set is bound to   CDA.participant.AssociatedEntity.classCode
  • Issue 33 "Value set epSOSTimingAddress without dataset binding" with status "Closed". Last event (2016-03-17T18:04:08):
    used in the telecom/@use attribute
  • Issue 37 "Value set epSOSDisplayLabel without dataset binding" with status "Rejected". Last event (2016-03-17T18:04:36):
  • Issue 38 "Two different descriptions in the documentation" with status "Open". Last event (2016-03-17T17:57:26):
  • Issue 39 "Element Indication" with status "Deferred". Last event (2017-05-17T14:36:22):
    Any analysis about the dataset is deferred
  • Issue 42 "Status" with status "Closed". Last event (2016-03-29T17:36:26):
    Changed the status code description for SubstaceAdministration
  • Issue 43 "Name of the concept" with status "Deferred". Last event (2016-03-29T13:24:34):
    HCER and MRO are not priority for the time being (not part of the guidelines)

    Data set element should be revised accoridng to the EU guidelines

  • Issue 47 "Missing value set binding for Health Care Alert code" with status "Closed". Last event (2016-04-22T09:16:13):
    Added the specification text to the comment field of the parent data element container
  • Issue 48 "Missing value set binding for Treatment code" with status "Closed". Last event (2016-04-04T15:28:28):
    No value set binding needed at this point in time.
  • Issue 49 "Missing value set binding for Prescriber Speciality" with status "Closed". Last event (2016-04-04T15:27:50):
    Mentioned HP Specialty is sufficient for now. Not value set binding necessary.
  • Issue 50 "Missing concepts for Dispenser?" with status "Closed". Last event (2016-03-29T13:21:57):
  • Issue 51 "Specialization of template "1.3.6.1.4.1.19376.1.5.3.1.2.4"" with status "Open". Last event (2016-07-13T16:57:24):
  • Issue 52 "Cardinality/nullFlavor for address (parts)" with status "Closed". Last event (2017-05-17T14:44:00):
    This is handled by the AD.EPSOS specialization of the AD datatype
  • Issue 53 "HP can have only 1 relevant speciality in a given context" with status "Open". Last event (2016-03-17T17:42:05):
  • Issue 54 "MRO has impossible card on performer/assignedEntity" with status "Rejected". Last event (2016-03-17T17:08:20):
    No fix required for the DECOR template.
  • Issue 55 "Assignement of an epSOS template ID for this section" with status "Open". Last event (2016-07-13T14:52:49):
  • Issue 56 "Identification of the IHE PCC template version actually used" with status "Closed". Last event (2016-04-04T16:09:57):
    Checked
  • Issue 57 "Informant role" with status "Open". Last event (2016-07-13T14:54:45):
  • Issue 58 "Assign an epSOS specific template ID" with status "Open". Last event (2016-07-13T14:51:30):
  • Issue 59 "Optionaly of template IDs" with status "Open". Last event (2015-11-09T15:26:26):
    Finding:

    The current specs requires that all the IHE PCC (simple obs ad socila Obs) and the CCD template IDs are provided .

    IHE PCC template just says that "These <templateId> elements identify this as a Social History observation." without indicating any optionality.

    Suggestion:

    Evaluate if is really needed that all of them would be required.

    Further explanation:

    This applies to several other templates

  • Issue 60 "Update example" with status "Closed". Last event (2017-05-17T14:39:29):
    removed the not used elements
  • Issue 61 "types of social observation" with status "Open". Last event (2015-11-09T15:43:47):
    Finding:

    the conceptual model consider only three types of social observation:

    • Smoke
    • Alcohol

    • Diet

    Suggestion:

    Evaluate if we need to specialize the IHE PCC template considering three different specialized template for each of them

    Further explanation:

    in the case of diet a coded element is excpected in the obs.value , but the epSSO MVC doesn't define such a type of value set

  • Issue 62 "Relationship between the type of obs.code and type of obs.value " with status "Open". Last event (2016-07-13T14:53:06):
  • Issue 63 "version of referenced specification" with status "Closed". Last event (2016-03-29T17:02:51):
    versions of the IHE TFs have been updated
  • Issue 64 "Assign an epSOS specific template ID" with status "Open". Last event (2017-08-01T19:05:36):
    I support this. id is mandatory in IHE template, but this does not make sense here (changed it to 0..1 R).
  • Issue 65 "routeofAdm and apporach site" with status "Closed". Last event (2017-05-17T13:52:29):
    Removed the binding 
  • Issue 66 "approachSiteCode" with status "Closed". Last event (2017-05-17T14:13:26):
    the approachSiteCode seems to be no more in the template...assumed closed
  • Issue 67 "doseQuantity duplicated" with status "Closed". Last event (2015-11-19T15:56:37):
    doseQuantity is now only one element with data type RTO_PQ_PQ
  • Issue 68 " 2.16.840.1.113883.10.20.1.46 Position Of Vaccination" with status "Closed". Last event (2016-03-17T11:26:57):
    Element removed
  • Issue 69 " adverse reactions in immunization" with status "Closed". Last event (2016-02-23T13:17:25):
  • Issue 70 "Product information duplicated ?" with status "Closed". Last event (2016-03-17T17:39:43):
    removed the "duplicated" relationship with product
  • Issue 71 "manufacturerOrganization in immunization product" with status "Closed". Last event (2015-11-19T16:01:42):
    manufacturerOrganization element eliminated
  • Issue 72 "Update the value sets based on latest MVC" with status "Closed". Last event (2017-11-15T16:14:01):
    Solved by loading the latest MVC version 2.2.2
  • Issue 73 "Revision of Section Coded Results" with status "Closed". Last event (2016-07-13T17:05:47):
    Template ID updated
  • Issue 74 "Revision of Section Allergies and Other Adverse Reactions" with status "Closed". Last event (2015-12-30T15:30:09):
    1.3.6.1.4.1.19376.1.5.3.1.4.5.3 Allergy and Intolerance Concern
    • statusCode shall be active|suspended|aborted|completed only, while whole Value Sets ActStatus is bound. Corrected.
    1.3.6.1.4.1.19376.1.5.3.1.4.6 Allergies And Intolerances
    • Allergen (participant typeCode CSM) is conditional 0..* to Observation.value. Condition added :: Omit if Observation.value is SNOMED-CT 160244002 No known Allergies
  • Issue 75 "Revision of Sections History of Past Illness and Active Problems" with status "Closed". Last event (2015-11-23T16:36:46):
  • Issue 76 "Revision of Section Coded List of Surgeries" with status "Closed". Last event (2017-05-17T13:49:54):
  • Issue 77 "Revision of Section Medical Devices Coded" with status "Closed". Last event (2017-08-01T18:46:34):
    IHE 1.3.6.1.4.1.19376.1.5.3.1.1.5.3.5 actually reauires section.id
  • Issue 78 "Revision of Section Health Maintenance Care Plan" with status "Closed". Last event (2016-03-18T15:07:15):
    the actual optionality of this template id is not well specified neither in the IHE PCC nor in the epSOS specs.

    The schematron published by IHE requires this element for the IHE PCC template. Change the cardinality from 0..1 to 1..1
  • Issue 79 "Revision of Section Functional Status" with status "Closed". Last event (2015-11-21T16:32:42):
    Section revised
  • Issue 80 "Revision of Section Pregnancy History" with status "Closed". Last event (2016-04-04T14:41:36):
    Reviewed Templates and pending issues, added a few new issues.
    Revision is closed.
  • Issue 81 "Revision of Section Coded Vital Signs" with status "Closed". Last event (2016-03-17T10:53:01):
  • Issue 82 "Revision section Coded Results" with status "Cancelled". Last event (2015-11-25T11:22:52):
    duplicated item
  • Issue 83 "DoseQuantity DT to be fixed" with status "Closed". Last event (2015-11-24T18:48:27):
    This was definitely entered/defined in error. doseQuantity is now a IVL_PQ as defined in the generic CDA.
  • Issue 84 "No Value Set for coding Invalidity" with status "Open". Last event (2015-11-21T16:29:47):
    Finding:

    This is a known issue. No Value set have been identified for describing autonomy/invalidity

    Suggestion:

    -

    Further explanation:

    -

  • Issue 85 "Concern entry ID" with status "Closed". Last event (2017-05-17T14:09:48):
    changed to required
  • Issue 86 "concern entri statuscode voc binding" with status "Closed". Last event (2017-05-17T14:08:31):
    added new value set and binding
  • Issue 87 "Constrains on IVL_TS" with status "Closed". Last event (2015-11-30T16:39:52):
    Fixed
  • Issue 88 "negationInd" with status "Closed". Last event (2016-04-04T16:08:29):
    Added negationInd isOptional=true
  • Issue 89 "Data type of the obs.code" with status "Closed". Last event (2017-05-17T12:22:07):
    datatypes updated
  • Issue 90 "check obs.ocde voc binding" with status "Open". Last event (2016-07-13T16:42:39):
  • Issue 91 "value set binding for Obs.value" with status "Open". Last event (2016-07-13T14:52:31):
  • Issue 92 "the referenced entry ID to be updated" with status "Open". Last event (2016-07-13T16:42:59):
  • Issue 93 "add attributes to the entryRelationship" with status "Closed". Last event (2015-11-23T12:39:36):
    Agree, done
  • Issue 94 "severity: the text shall contain a ref " with status "Closed". Last event (2015-11-23T12:42:23):
    Agree, done
  • Issue 95 "statusCode required ?" with status "Closed". Last event (2015-12-30T15:27:39):
    statusCode shall be present in all cases and values "completed" due to the underlying (derived from) specifications; Changes in the templates.
  • Issue 96 "obs.value add constrains" with status "Closed". Last event (2015-11-25T11:25:25):
    data type changed to CD.EPSOS
  • Issue 97 "assign an epSOS template ID" with status "Open". Last event (2016-07-13T16:43:22):
  • Issue 98 "Text element: add constrain" with status "Closed". Last event (2015-12-30T15:03:16):
    Done
  • Issue 99 "Comment Author" with status "Open". Last event (2016-07-13T14:51:51):
  • Issue 100 "rename to "Medication Item""" with status "Closed". Last event (2015-11-24T18:53:57):
    The Template's business name and display name has been set accordingly
  • Issue 101 "templates for Normal Dosing, split dosing and combination medication" with status "Deferred". Last event (2017-05-17T13:54:38):
    In case to be reconsidered for future discussion
  • Issue 102 "Medication entry cardinality" with status "Closed". Last event (2015-11-25T11:05:15):
    entry changed to 1..* R
  • Issue 103 "Revision of Section Medication Summary" with status "Closed". Last event (2016-03-01T12:31:10):
  • Issue 104 "Text in description" with status "Deferred". Last event (2016-03-17T17:27:45):
    This an optional section used to say i know she is pregnant. Up to now all the oter cases has been managed skipping the section.

    The way to manage negations, not known information need to be faced more widely. 
  • Issue 105 "section code correct?" with status "Deferred". Last event (2015-11-25T11:18:04):
  • Issue 106 "should-language" with status "Closed". Last event (2015-11-25T11:04:09):
    The code is thus declared to be mandatory 1..1 M, ie no null flavors are allowed. That is correct in spec and ART-DECOR.

    The phrase "the code should come from this list" equals to a binding to the value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.9 epSOSPregnancyInformation (Dynamic) with CWE coding strength (coded with exceptions), saying that if a concept fits one of the codes in the value set this code must be used, otherwise other codes may be used (from other code systems).

    Changed codings strength to CWE
  • Issue 107 "cardinality observation/value" with status "Closed". Last event (2015-11-25T11:03:18):
    Then the spec needs to be corrected.
    M means no null flavors are allowed (mandatory). This is in principal equal to SHALL.
    R means null flavors are allowed (required).
    Null Flavors should be allowed here for sure.

    Changed to 1..1 R
  • Issue 108 "section code is for document, details to be added" with status "Open". Last event (2015-11-25T11:02:56):
    Finding:

    - The LOINC code used here signifies a document, not a section. Furthermore, it asks for specification of {setting} and {Author Type}. Not sure if this is appropriate code here.

    Suggestion:

    - Check for alternative, possibly request new code from LOINC

    Further explanation:

    -

  • Issue 109 "restriction to past surgeries" with status "Deferred". Last event (2017-05-17T13:49:37):
    To be reconsidered in the future
  • Issue 110 "cardinality of Procedure entry" with status "Closed". Last event (2015-11-26T16:35:29):
    Added this text to Procedure entry
  • Issue 111 "Change Section.code to be standard" with status "Closed". Last event (2015-11-25T11:12:27):
    Was entered in ART-DECOR in error, is now the correct LOINC code for Section.code
  • Issue 112 "effectiveTime mandatory, NullFlavor not allowed? discussion needed" with status "Closed". Last event (2015-11-26T15:57:07):
    Done
  • Issue 113 "Missing id in template" with status "Closed". Last event (2015-11-25T13:00:10):
    Element id added as 0..* R
  • Issue 114 "Code no value set bound" with status "Closed". Last event (2015-11-25T13:01:03):
    Observation.code now bound to epSOSBloodPressure value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.21
  • Issue 115 "More codes in value set" with status "Open". Last event (2015-11-25T12:39:27):
    Finding:

    Only a few concepts in associated value set Obs.code

    Suggestion:

    In the future a value set should contain much more concepts, see e.g. ELGA_Vitalparameterarten 1.2.40.0.34.10.34

    Further explanation:

    -

  • Issue 116 "Add text element" with status "Closed". Last event (2015-11-26T15:51:40):
    Done
  • Issue 117 "statusCode missing" with status "Closed". Last event (2015-11-26T15:35:19):
    Done
  • Issue 118 "Use of methodCode and targetSiteCode" with status "Closed". Last event (2016-03-29T16:51:44):
    Those elements had value sets associated. They were included in the template, but not accepted by functional experts as part of the Patient Summary data set.

    Left as optional element without voc bunding only for future consideration. Added a note in the template description.
  • Issue 119 "Multiplicity in EntrySimpleObservation" with status "Closed". Last event (2015-11-26T15:19:25):
    Done as planned
  • Issue 120 "Update the actStatus" with status "Closed". Last event (2017-05-17T14:33:44):
    defined a new VS and added a binding
  • Issue 121 "Name of Template Medicine & specialized templates" with status "Open". Last event (2017-05-17T13:55:00):
  • Issue 122 "Typo in Description" with status "Closed". Last event (2016-03-01T12:56:49):
  • Issue 123 "epsos:asSpecializedKind/classCode" with status "Closed". Last event (2017-05-17T10:03:43):
    updated
  • Issue 124 "asSpecializedKind missing in Medication Summary Spec" with status "Open". Last event (2016-03-17T10:04:14):
  • Issue 125 "Fix statusCode definitions" with status "Closed". Last event (2015-12-02T22:50:41):
    Done
  • Issue 126 "Add 1.3.6.1.4.1.12559.11.10.1.3.1.3.1 template specializations" with status "Open". Last event (2016-07-13T16:42:19):
  • Issue 127 "manufacturedProduct/manufacturedMaterial/code remove voc binding" with status "Closed". Last event (2017-05-17T12:20:14):
    Removed the binding
  • Issue 128 "asSpecializedKind/epsos:generalizedMedicineClass/epsos:code voc binding missing" with status "Closed". Last event (2017-05-17T12:17:17):
    template upodated
  • Issue 129 "add manufacturedProduct/manufacturedMaterial/epsos:asSpecializedKind/epsos:generalizedMedicineClass/epsos:name element" with status "Closed". Last event (2017-05-17T13:46:38):
    template updated
  • Issue 130 "ingredient/[@classCode='ACTI']/ingredient/code element missing" with status "Closed". Last event (2017-05-17T12:15:49):
    Updated the template
  • Issue 131 "supply.code not foreseen" with status "Closed". Last event (2017-05-17T13:57:15):
    removed the voc binding
  • Issue 132 " hl7:effectiveTime datatype" with status "Closed". Last event (2017-05-17T14:24:28):
    added datatype and one example with the time stamp
  • Issue 133 "participantRole.id is optional" with status "Closed". Last event (2016-03-17T10:03:10):
    Added cardinality 0..*
  • Issue 134 "No devices example" with status "Open". Last event (2016-07-13T16:59:10):
    Improvement planned for the next template version (assigned to the label Template ID even if it is not related to this)
  • Issue 135 "Assign an epSOS specific template" with status "Open". Last event (2016-07-13T14:53:33):
  • Issue 136 "section.id optionality" with status "Closed". Last event (2017-05-17T13:37:16):
    Made Optional
  • Issue 137 "change oid of the template included for the organizer" with status "Open". Last event (2017-05-17T13:53:02):
  • Issue 138 "Add contrains for the organizer attributes" with status "Closed". Last event (2017-05-17T14:16:53):
    updated
  • Issue 139 "change the constrain about code@displayName" with status "Closed". Last event (2016-03-17T11:45:20):
    As epsom is multilingual, the constraint on having displayName valued as "Vital Signs" has been removed 
  • Issue 140 "Check effectivetime datatype" with status "Closed". Last event (2016-03-17T11:49:52):
    Added explanation and two examples
  • Issue 141 "change the reference for the Vital Signs Obs" with status "Closed". Last event (2016-03-17T11:13:08):
    Done
  • Issue 142 "Improve example, it is too generic." with status "Closed". Last event (2017-05-17T10:30:42):
    added id and effectiveTime
  • Issue 143 "Defunct Link to Template SimpleObservation" with status "Deferred". Last event (2017-05-17T11:18:28):
    No broken links in the template specifications; references to external templates used by /uses is not relevant for the time being . to be reconsidered for future consideration
  • Issue 144 "Relation Specialization defunct link" with status "Rejected". Last event (2017-05-17T10:35:07):
    Not clear what was the issue the 1.3.6.1.4.1.19376.1.5.3.1.3.11 is defined in the IHE PCC and it is the parent of this template
  • Issue 145 "Include footnote from Text Spec" with status "Closed". Last event (2017-05-17T10:15:05):
    Note added in the description
  • Issue 146 "Add epSOS unstructured document specifcations " with status "Closed". Last event (2017-05-17T09:59:45):
    Added proposal templates for unstructured documents
  • Issue 147 "Update document according to CP#08" with status "Open". Last event (2016-07-06T10:47:50):
    Finding:

    According to CP#8 the optionality R/R/RFNA shall be read as RNFA / RNFA / RNFA

    Suggestion:

    Update the work document consequently

  • Issue 148 "update specialty cardinality to 0..1" with status "Open". Last event (2016-07-06T10:49:40):
    Finding:

    Update Specialty cardinality to 0..1 (table in § 10.1)

    Suggestion:

    -

    Further explanation:

    -

  • Issue 149 "Value set 2.16.840.1.113883.1.11.19708 ActSubstanceAdministrationCode" with status "Closed". Last event (2017-05-17T09:57:34):
    Binding removed
  • Issue 150 "Fix participant role for agents" with status "Open". Last event (2017-05-17T14:49:33):
    TO BE FIXED creating a template fragment for agents
  • Issue 151 "statusCode cardinality to 1..1" with status "Closed". Last event (2017-05-17T09:54:40):
    fixed to 1..1
  • Issue 152 "IHE PCC templateId entry cannot be required" with status "Closed". Last event (2017-05-17T09:30:56):
    changed cardinality of the "other" templates to 0..1
  • Issue 153 "Example: Invalid XML" with status "Deferred". Last event (2017-05-17T14:52:25):
    no more able to see where the problem was...maybe it has been fixed
  • Issue 154 "Update the doseQuantity description " with status "Closed". Last event (2017-05-17T09:50:00):
    description updated
  • Issue 155 "Clarification on the usage of doseQuanity" with status "Closed". Last event (2017-05-17T09:51:17):
    Updated the doseQuantity description
  • Issue 156 "Assert not aligned with the error message" with status "Open". Last event (2017-05-17T14:54:30):
  • Issue 157 "Cardinality of the name prefix and suffix" with status "Closed". Last event (2017-11-15T17:00:10):
    This issue is related to issue 161 and the cardinality of the prefix/suffix is changed to 0 ... * (which is compliant with the HL7 CDA specifications)
  • Issue 158 "SignatureCode fixed to "S"" with status "Closed". Last event (2017-05-17T09:20:35):
    Added fixed code S
  • Issue 159 "relatedDocument cardinality" with status "Closed". Last event (2017-05-17T09:24:53):
    changed to 1...*
  • Issue 160 "Cardinality Contact/Preferred HP/Legal Organization" with status "In Progress". Last event (2017-05-17T14:53:57):
  • Issue 161 " (epSOSCDAauthor): prefix and suffix is required for assignedPerson" with status "Closed". Last event (2017-05-17T09:23:23):
    Changed the cardinailty for authior and legal auth.
  • Issue 162 "Check and update EDQM OID" with status "Closed". Last event (2017-11-15T15:30:33):
    Solved by the loading of the new MVC 2.2.2
  • Issue 163 "Check the binding with language VS" with status "Open". Last event (2017-05-17T14:53:29):
  • Issue 164 "realmCode" with status "Open". Last event (2017-07-18T23:26:34):
    Finding:

    -realmCode is Mandatory

    Suggestion:

    -change to 0..1 R

    Further explanation:

    -

  • Issue 165 "realmCode" with status "Open". Last event (2017-07-18T23:27:36):
    Finding:

    -is Mandatory

    Suggestion:

    --change to 0..1 R

    Further explanation:

    -

  • Issue 166 "realmCode" with status "Open". Last event (2017-07-18T23:26:57):
    Finding:

    -is mandatory

    Suggestion:

    --change to 0..1 R

    Further explanation:

    -

  • Issue 167 "realmCode" with status "Open". Last event (2017-07-18T23:28:55):
    Finding:

    -is mandatory

    Suggestion:

    --change to 0..1 R

    Further explanation:

    -

  • Issue 168 "realmCode" with status "Open". Last event (2017-07-18T23:28:19):
    Finding:

    -is Mandatory

    Suggestion:

    --change to 0..1 R

    Further explanation:

    -

  • Issue 169 "classCode, determinerCode" with status "Feedback needed". Last event (2017-07-18T23:01:19):
    proposal to close.

    I implemented the change. Expecting little effect, because it just removes (unnecessary) constraints.
  • Issue 170 "elements in address" with status "Open". Last event (2017-07-18T23:22:21):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    epSOS said for most address occurrences: "If there is no information, the nullFlavor attribute shall have a value of 'NI' and no address parts shall be present, otherwise there shall be no nullFlavor attribute, and at least one of the address parts listed below shall be present.". Only for Healthcare Facilities there are stricter rules (R1.10.9.3). From the information on optionality it can be inferred that the intention was to make only country mandatory here. Changed accordingly.

    -

  • Issue 171 "multiple instances of effectiveTime" with status "Open". Last event (2017-07-18T23:21:44):
    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:

    -

  • Issue 172 "classCode, moodCode" with status "Rejected". Last event (2017-11-16T15:27:04):
    Change rejected. This is a specialization of Template CDA documentationOf (prototype, directly derived from POCD_RM000040 MIF).
  • Issue 173 "prefix/suffix required" with status "Closed". Last event (2017-11-16T15:38:54):
    Looks okay, is the same as the other person instances. Closed.
  • Issue 174 "Allow serviceEvent/effectiveTime as interval or TS?" with status "Open". Last event (2017-05-31T19:06:55):
    Finding:

    - EffectiveTime of ServiceEvent required Low and high

    Suggestion:

    - Modify template to allow for high only (without low) and also allow for TS, alternatively ("silent demotion")

    Further explanation:

    -

  • Issue 175 "OID for Comment Template" with status "Open". Last event (2017-06-08T13:01:07):
    Finding:

    The OID for the Comment Entry here is the same as for the IHE Comment Entry from PCC. You cannot use the same OID as it defines additional constraints here.

    Suggestion:

    Use the IHE Comment Entry as-is (ref) or clone it with a new template ID.

    Further explanation:

    -

  • Issue 176 "CDA Device : check value set binding with device.code" with status "Open". Last event (2017-06-12T17:44:51):
    Finding:

    To be evaluate if the value set indicated "The value of @code shall be drawn from value set  2.16.840.1.113883.1.11.16040 EntityCode  (DYNAMIC)" is here appropriate.

    Suggestion:

    -

    Further explanation:

    -

  • Issue 177 "Preferred Health Professional for emergency contact: change the classCode to ECON" with status "Open". Last event (2017-06-13T12:04:11):
    Finding:

    To describe the Preferred Health Professional for emergency contact is currently used participant/functionCode = PCP and particiapnt/associatedEntity@classCode="PRS"

    The usage of the classCode ECON seems to be more appropriate.

    Suggestion:

    -

    Further explanation:

    -

  • Issue 178 "No Entry?" with status "Open". Last event (2017-06-30T11:26:04):
    Which section Libor?
  • Issue 179 "generic template for simple observation is ill-defined" with status "Closed". Last event (2017-07-18T22:31:52):
    done.
  • Issue 180 "classCode is mandatory" with status "Open". Last event (2017-07-18T23:19:34):
    Finding:

    - classCode is mandatory, according to schema

    Suggestion:

    - change cardinality from 0..1 to 1..1

    Further explanation:

    -

  • Issue 181 "observation classCode is mandatory" with status "Open". Last event (2017-07-14T12:19:00):
    Finding:

    - observation classCode is mandatory

    Suggestion:

    - change cardinality to 1..1

    Further explanation:

    -

  • Issue 182 "change hl7:languageCode description" with status "Open". Last event (2017-07-14T12:20:15):
    Finding:

    At the moment the description is:
    Document Language Code
    • The language code SHALL be in the form nn-CC.
    • The nn portion SHALL be an ISO-639-1 language code in lower case derived by the Value Set epSOSLanguage.
    • The CC portion SHALL be an ISO-3166 country code in upper case derived by the value Set epSOSCountry
    Suggestion:

    Since MVC 2.2.1, the epSOSLanguage Value set contains already the languageCodes in the form nn-CC, so the hl7:languageCode won't be composed by the epSOSLanguage and the epSOSCountry codes with a hyphen in between.

    Further explanation:

    -

  • Issue 183 "LOINC code for blood group observation" with status "Open". Last event (2017-07-18T22:55:45):
    also see discussion on LOINC code in epsos-issue-192
  • Issue 184 "displayname and codesystem name are optional" with status "Open". Last event (2017-07-18T23:20:00):
    AFAIK the datatypes of such codes need to be CD.EPSOS rather than the generic CD
  • Issue 185 "Template is too specific" with status "Feedback needed". Last event (2017-07-19T11:25:51):
    The Coded Results Section template (1.3.6.1.4.1.12559.11.10.1.3.1.2.5) accepts only blood group observation ( 1.3.6.1.4.1.19376.1.5.3.1.4.13.6)  and no other observation entries . This requirement is listed as R18.1 and R18.2 in the PDF spec, and copied in the current template spec.
  • Issue 186 "allow for multiple entries" with status "Closed". Last event (2017-07-18T22:58:53):
    proposal to close issue. 

    implemented the proposed change, tests showed that it enables the documentation of both, closed and open Allergy Concerns in the same section.
  • Issue 187 "units in ingredient/quantity" with status "Feedback needed". Last event (2017-07-18T23:19:06):
    I'm not sure without re-reading our manual but I think if the binding is CWE a warning is generated instead of an error.
  • Issue 188 "Dosing-specific templates do not appear in template ID list" with status "Open". Last event (2017-07-18T15:21:05):
    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
  • Issue 189 "correct OID for EDQM standard terms" with status "Closed". Last event (2017-11-15T15:29:22):
    Solved by the loading of the new MVC 2.2.2
  • Issue 190 " correct OID for EDQM standard terms" with status "Closed". Last event (2017-11-15T15:30:03):
    Solved by the loading of the new MVC 2.2.2
  • Issue 191 "correct OID for EDQM standard terms" with status "Closed". Last event (2017-11-15T15:28:50):
    Solved by the loading of the new MVC 2.2.2
  • Issue 192 "revert to original IHE template" with status "Feedback needed". Last event (2017-07-18T22:54:41):
    suggest to close issue, after discussion.
  • Issue 193 "empty template ID" with status "Closed". Last event (2017-07-18T22:53:14):
    change implemented
  • Issue 194 "template editor does not open" with status "Closed". Last event (2017-07-18T23:10:05):
    problem does not occur anymore, I was able to edit the template. issue solved.
  • Issue 195 "XML namespace for epSOS medication extensions" with status "Closed". Last event (2017-07-27T20:36:16):
    Changed to urn:epsos-org:ep:medication
  • Issue 196 "Fix some Cx.EPSOS DT definitions" with status "Closed". Last event (2017-07-22T11:39:45):
    Apologies, this was a documentation error and not a definition error. The documentation has been updated to reflect the current situation. Thanks for your patience.
  • Issue 197 "allow for multiple entries" with status "Open". Last event (2017-07-27T18:25:13):
    Finding:

    - cardinality of entry is 0..1

    Suggestion:

    - change to 0..*

    Further explanation:

    - good practice is to have one entry to contain one ProblemConcernAct, containing one Problem observation.

  • Issue 198 "allow for multiple entries" with status "Closed". Last event (2017-07-27T18:28:34):
    Finding:

    -section allows only 0..1 entry

    Suggestion:

    - change to 0..*

    Further explanation:

    - It is good practice that one entry contains one Act containing one Problem. So for multiple past illnesses we need multiple entries.

  • Issue 199 "doseQuantity: value set binding for units" with status "Open". Last event (2017-07-27T20:46:38):
    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.
  • Issue 200 "value set for illnesses and disorders needs to be updated to four-digit ICD-10" with status "Closed". Last event (2017-07-27T21:54:44):
    Finding:

    - The current value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.5 does not reflect the most recent version of MVC

    Suggestion:

    - should be updated to contain 4 -digit ICD codes

    Further explanation:

    -

  • Issue 201 "Update to 4-char ICD" with status "Closed". Last event (2017-07-28T10:00:44):
    Finding:

    - Value set does not follow the updates in MVC

    Suggestion:

    - Suggest to update the value set.
    Please clarify with Solution Provider Terminology Expert how to proceed...

    Further explanation:

    -

  • Issue 202 "act.id conformance: not mandatory" with status "Closed". Last event (2017-08-01T18:32:51):
    Finding:

    - act.id is mandatory

    Suggestion:

    - change to 0..1 R

    Further explanation:

    - no reason to have it mandatory in base templates.

  • Issue 203 "editorial change: clarification concerning ActCode codesystem" with status "Closed". Last event (2017-08-01T18:56:13):
    Finding:

    - Description doesn't make it clear that codeSystem IHEActCode (1.3. 5.1.4.1.19376.1.5.3.2) must be used, and not generic HL7 ActCode (2.16.840.1.113883.5.4)

    Suggestion:

    - add text to clarify

    Further explanation:

    -

  • Issue 204 "id cardinality should be 0..1" with status "Closed". Last event (2017-08-01T19:09:19):
    Finding:

    - id cardinality is 1..1 R

    Suggestion:

    - id cardinality should be 0..1 R

    Further explanation:

    -

  • Issue 205 "id cardinality" with status "Open". Last event (2017-08-01T19:40:28):
    Finding:

    - is 1..1 R

    Suggestion:

    - should be 0..1 R

    Further explanation:

    -

  • Issue 206 "Define a specialized template for the agent" with status "Open". Last event (2017-09-05T12:04:37):
    Finding:
    hl7:participant
    0 … * C

    The substance that causes the allergy or intolerance shall be specified in the <participant> structure.

    The <code> element shall be present. It may contain a code and codeSystem attribute to indicate the code for the substance causing the allergy or intolerance. It shall contain a <reference> to the <originalText> in the narrative where the substance is named.


    Contains 2.16.840.1.113883.3.1937.777.11.10.134 CDA Participant (Body) (DYNAMIC)
    Suggestion:

    A specialized template should be defined for the <participant> structure describing the substance that causes the allergy or intolerance

    Further explanation:

    -

  • Issue 207 "Support for Multiple Active ingredient in ART-DECOR" with status "Closed". Last event (2017-10-12T16:05:22):
    Yes, it looks like an error in the current IG version. In the original PDF spec under rule R4.3 we see that manufacturedMaterial/ingredient/[@classCode='ACTI']/ingredient/name is on the same lavel as manufacturedMaterial/ingredient/[@classCode='ACTI']/ingredient/code

    Also, the levels of originalText and translation are strange. I believe they should be under manufacturedMaterial/ingredient/[@classCode='ACTI']/ingredient/code.

    I changed the template, moving originalText and translation under code, and moving name to the same level as code.
  • Issue 208 "Schema Error for draft element "hl7:desc" " with status "Closed". Last event (2017-10-27T16:22:22):
    Solved by changing the namespace prefix from hl7 to epsos
  • Issue 209 "Constraint applied to relatedDocument" with status "Open". Last event (2017-10-27T17:42:06):
    Finding:

    The CDA standard claims
    "A conformant CDA document can have a single relatedDocument with typeCode "APND"; a single relatedDocument with typeCode "RPLC"; a single relatedDocument with typeCode "XFRM"; a combination of two relatedDocuments with typeCodes "XFRM" and "RPLC"; or a combination of two relatedDocuments with typeCodes "XFRM" and "APND".

    No other combinations are allowed."

    Suggestion:

    This constraint is not captured by the current specifications.
    Add an explicit assertion to check this.

    Further explanation:

    -

  • Issue 210 "wrong cardinality of section/id" with status "In Progress". Last event (2017-10-28T00:14:23):
    Finding:

    - cardinality of id is 0..*

    Suggestion:

    - must be maximum 1. 
    Changed it to 0..1

    Further explanation:

    -

  • Issue 211 "statusCode cardinality wrong" with status "Closed". Last event (2017-10-28T09:59:41):
    Changed to 1..1
  • Issue 212 "cardinality of manufacturedProduct" with status "In Progress". Last event (2017-10-28T00:34:51):
    Finding:

    - cardinality of manufacturedProduct must be less or equal 1

    Suggestion:

    - Changed to 0...1

    Further explanation:

    -
    Test :  CDATEMP005(Validation Level : FLATTEN_4 , Type : ERROR) 
    Location :  //rules/template[14]/element[1]/element[16]/element[1] 
    CDALocation :  /hl7:substanceAdministration[hl7:templateId/@root='1.3.6.1.4.1.12559.11.10.1.3.1.3.2']/hl7:consumable/hl7:manufacturedProduct 
    Description :  The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005] 

  • Issue 213 "can not have more than one legalAuthenticator" with status "Closed". Last event (2017-10-28T10:02:51):
    If an artefact is locked but no longer used (e.g. if somebody opened the editor and simply clicked it away instead of closing it through the save or cancel buttons) the locks can be deleted by any project author through the Project -> Status tab.

    The cardinality has been changed to 1..1
  • Issue 214 "Base Standard Validation" with status "Open". Last event (2017-10-29T10:18:19):
    Finding:

    When <let> used, it shall not contains circular references to other <let> elements [HL7TEMP-045]  

    Suggestion:

    - more information needed.

    Further explanation:

    -

  • Issue 215 "effectiveTime maximum multiplicity " with status "Open". Last event (2017-10-29T10:25:38):
    Finding:

    - effectiveTime has cardinality 1..*

    Suggestion:

    -The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]  

    Further explanation:

    -

  • Issue 216 "text: maximum multiplicity" with status "In Progress". Last event (2017-10-29T10:28:05):
    Finding:

    - text cardinality is 1...*

    Suggestion:

    The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]

    Further explanation:

    -

  • Issue 217 "effectiveTime maximum multiplicity" with status "In Progress". Last event (2017-10-29T10:29:16):
    Finding:

    - effectiveTime is 1..*

    Suggestion:

    -The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]  

    Further explanation:

    -

  • Issue 218 "substanceAdministration maximum multiplicity" with status "In Progress". Last event (2017-10-29T10:59:01):
    Finding:

    - substanceAdministration maximum multiplicity is *

    Suggestion:

    The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]  

    Further explanation:

    -

  • Issue 219 "Constraints for custodian organization" with status "Open". Last event (2017-10-29T12:50:15):
    Finding:

    - The cardinality of custodian telecom is 0..* here, while it is constrained to 0..1 in the CDA Spec for custodiaon Org. Moreover, ID is mandatory for Custodian organisation.

    Suggestion:

    - cannot use the generic Organization template here. Adapt to additional constraints, specific for custodian organization.

    Further explanation:

    -

  • Issue 220 "see epsos-issue-219" with status "Open". Last event (2017-10-29T11:11:27):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 221 "can not have more than one legalAuthenticator" with status "In Progress". Last event (2017-10-29T11:12:49):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 222 "fix cardinality" with status "In Progress". Last event (2017-10-29T11:19:01):
    Finding:

    - cardinality is 0..*

    Suggestion:

    The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]  

    Further explanation:

    -

  • Issue 223 "fix cardinality" with status "Open". Last event (2017-10-29T11:22:06):
    Finding:

    -Test :  CDATEMP005(Validation Level : FLATTEN_4 , Type : ERROR) 

    Location :  //rules/template[31]/element[1]/element[10]/element[1]/element[3] 
    CDALocation :  /hl7:substanceAdministration[hl7:templateId/@root='1.3.6.1.4.1.19376.1.5.3.1.4.12']/hl7:consumable/hl7:manufacturedProduct/hl7:manufacturedMaterial 
    Description :  The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]  Suggestion:

    -

    Further explanation:

    -

  • Issue 224 "fix cardinality" with status "In Progress". Last event (2017-10-29T11:25:08):
    Finding:

    -Test :  CDATEMP005(Validation Level : FLATTEN_4 , Type : ERROR) 

    Location :  //rules/template[36]/element[1]/element[6] 
    CDALocation :  /hl7:observation[hl7:templateId/@root='1.3.6.1.4.1.19376.1.5.3.1.4.13.5']/hl7:effectiveTime 
    Description :  The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]  Suggestion:

    -

    Further explanation:

    -

  • Issue 225 "custodian org, see epsos-issue-219" with status "Open". Last event (2017-10-29T11:37:19):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 226 "fix cardinality of status code" with status "In Progress". Last event (2017-10-29T11:42:29):
    Finding:

    -Test :  CDATEMP005(Validation Level : FLATTEN_4 , Type : ERROR) 

    Location :  //rules/template[42]/element[1]/element[5] 
    CDALocation :  /hl7:act[hl7:templateId/@root='1.3.6.1.4.1.19376.1.5.3.1.4.3.1']/hl7:statusCode 
    Description :  The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]  Suggestion:

    -

    Further explanation:

    -

  • Issue 227 "custodian org, see epsos-issue-219" with status "Open". Last event (2017-10-29T11:44:51):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 228 "custodian org, see epsos-issue-219" with status "Open". Last event (2017-10-29T11:49:48):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 229 "custodian org, see epsos-issue-219" with status "Open". Last event (2017-10-29T11:57:11):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 230 "custodian org, see epsos-issue-219" with status "Open". Last event (2017-10-29T11:57:27):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 231 "participant: duplication of levels " with status "Open". Last event (2017-10-29T12:03:51):
    Finding:

    - The contains statement produces a duplication of the participant element (nesting).

    Suggestion:

    - replace "contains" by "include"?

    Further explanation:

    -

  • Issue 232 "participant duplication - see epsos-issue-231" with status "Open". Last event (2017-10-29T12:07:07):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 233 "Value Set differs from original normative CDA Spec" with status "Open". Last event (2017-10-30T13:56:47):
    sorry. The referenced value set is 2.16.840.1.113883.1.11.10901. And apparently it contains concepts that were not present in the original CDA vocabulary.

    The base standards validation complains:
    Test : CDATEMP019(Validation Level : FLATTEN_VOCAB , Type : FATALERROR) 
    Location : //rules/template[14]/element[1]/element[18]/attribute[1] 
    CDALocation : /hl7:substanceAdministration[hl7:templateId/@root='1.3.6.1.4.1.12559.11.10.1.3.1.3.2']/hl7:participant/@typeCode 
    Description : When a valueset is specified, and the referenced attribute is an enumeration, the content of the valueset SHALL be a restriction of the referenced attribute [CDATEMP-019] 
  • Issue 234 "The maximum multiplicity SHALL be lower or equals to the maximum multiplicity from the CDA model [CDATEMP-005]" with status "Closed". Last event (2017-10-31T08:55:15):
    I won't take any action on this:
    The template I changed ( 2.16.840.1.113883.3.1937.777.11.10.111 ) is the generic epSOSCDAOrganization, used for all kinds of Organizations.
    The bug was that Custodian should have a specialized template, more restrictive than the generic one that you changed.
  • Issue 235 "hl7:assignedPerson contains twice the element hl7:name" with status "In Progress". Last event (2017-10-31T18:09:56):
    The hl7:assignedPerson has a containment and and "overriding" inline definition. This is illegal. It should be either one.
    For the hl7:representedOrganization our recommendation is to name the representedOrganization element and the include the template (rather than contain).
    The same should be done for hl7:assignedPerson if appropriate.
  • Issue 236 "Relaxation of constraints for EntryAllergyAndIntolerance template" with status "Open". Last event (2017-11-03T11:18:21):
    Finding:

    In the Template EntryAllergyAndIntolerance   [1.3.6.1.4.1.19376.1.5.3.1.4.6]   in ART-DECOR, the hl7:id element is not consistent with the inheritance from the template Problem [1.3.6.1.4.1.19376.1.5.3.1.4.5]

    - The template EntryAllergyAndIntolerance   inherit from the template Problem, the template EntryAllergyAndIntolerance   says that hl7:id is 0..* , however the template Problem says that hl7:id is 1..1. This is not permitted to relax constraints.

    Suggestion:

    - Change the EntryAllergyAndIntolerance template and make the id a 1 ... 1 (with a conformance M?)

    Further explanation:

    -

Active
2015-11-07 15:17:27Dr. Kai U. HeitmannRelease: 2014
Intermediate release before changes during the EXPAND update and review project: Formalization of epSOS Patient Summary, ePrescription and eDispensation documents using ART-DECOR
Draft
2014-02-28Dr. Kai U. Heitmann (Nictiz)
Corrected several templates that contained illegal spaces in OIDs or codes
2013-12-03Alexander Henket (Nictiz)
Review version for Giorgio Cangioli
2013-06-09Alexander Henket (Nictiz)
Extended data set, vocabulary, templates
2013-06-04Tessa van Stijn (Nictiz)
Added scenario and HL7 templates
2013-05-30Maarten Ligtvoet (Nictiz)
First concept of the epSOS decor file for demonstration purposes
2013-05-30Elze de Groot (Nictiz)
Added data set and vocabulary
Busy
MyCommunity
Display NameNameDescription
BusyRetrieving…
Governance Groups
BusyRetrieving…
ART-DECOR Applications (ADA)
Application