# DECOR Information for Project: International Patient Summary (IPS) (hl7ips-)
Release 2.0.1 as of 2026‑02‑15 08:38:13 | | | HTML built on 2026‑02‑15 08:40:13

- Front Page
- Project Information
- Dataset
- Scenarios
- Identifiers
- Terminology
- Templates
- Issues
- Compile Time
- Legal

## Project Information

Project Goals
The goal of this project is to identify the required clinical data with associated vocabulary bindings and value sets for patient summary, in the context of specific use cases, and to build an international document and associated templates based on HL7 CDA R2 (or a future CDA release) and potentially the FHIR standards, with value sets to support data elements within those templates. The initial use cases will be the patient summary, providing support for emergency care and unplanned care.
The International Patient Summary (IPS) is intended to be "a minimal and non-exhaustive patient summary, specialty-agnostic, condition-independent, but readily usable by clinicians for the cross-border unscheduled care of a patient."
These templates/profiles aim to:

- Serve for both cross-jurisdictional (through adaptation/extension for multi-language and realm scenarios, including translation) and national (through localization) patient summaries.
- Support emergency care and unplanned care in any country (home and foreign), regardless of language
- Define value sets based on international vocabularies that are usable and understandable in any country

The deliverable(s) will address the requirements of an international patient summary:

- For the exchange of structured and coded information (section headings, entries)
- For administrative data in order to support content commitment, audit/logging/provenance

The project will receive input from the EHR WG regarding the specification of functional requirements on patient summaries.
This includes a compilation of the required clinical data, based on results of multiple previous projects on patient summaries (including but not limited to epSOS, ONC, Trillium Bridge, eHealth Exchange), rules and recommendations for the use and maintenance of associated vocabulary bindings and value sets (in multilingual settings), and templates for the implementation of international patient summary documents.
Therefore this project has its primary focus on provisions for semantic interoperability.
Templates/profiles should take in consideration, where applicable, legal, organizational, security and infrastructure requirements based on experiences of pilot implementations (Trillium Bridge).
The white paper on Comparative Analysis Between HL7 C-CDA R1.1 CCD and epSoS PS v1.4 will inform the development of the harmonized template and associated value sets.
Project Background
In 2010 a MoU was signed between EU and US to strengthen global cooperation in eHealth/Health. As a result, the ONC S&I “Interoperability of EHR” work group was launched in US in 2013 (http://wiki.siframework.org/EU-US+eHealth+Cooperation+Initiative) and the Trillium Bridge Project (www.trilliumbridge.eu) in Europe to compare the CDA templates specified at that time in Europe (epSOS PS V1.4) and in US (MU – C-CDA CCD v1.1) for Patient Summaries (PSs) and to build a Trans-Atlantic exchange proof of concept. Both initiatives resulted identifying the need for a common template and vocabularies for the Patient Summary, in particular the following recommendation was offered and endorsed by all members of the Joint Initiative Council and by the HL7 International Council: “to advance an International Patient Summary (IPS) standard and enable people to access and share their health information for emergency or unplanned care anywhere and as needed. At minimum the IPS should include immunizations, allergies, medications, clinical problems, past operations and implants.”
Meanwhile:

- A new version of the EU/US MOU Transatlantic eHealth/health IT Cooperation Roadmap entered consultation in November 2015 , ;
- (US) a Shared Nationwide interoperability roadmap was published in November 2015 ;
- The Joint Initiative Council (JIC) on SDO Global Health Informatics Standardization, initiated the standard sets project with patient summary as its pilot ;
- A maintenance process for the European Patient Summary Guidelines is in progress (expected release on Nov 2016);
- The European eHealth Digital Service Infrastructure (project for the operational deployment of the EU cross-borders services) has been launched (2016-2018)
- ART-DECOR® and the HL7 DSTU (now STU) template exchange format are being more and more used by European countries, including for the European Patient Summary templates (aka epSOS PS template). ART DECOR is also connected to the IHE

### Additional project information

This project is marked as a repository
Properties
Prefix: hl7ips-Default language: en-US Contains reusable content
Publication location | Project overview
--- | ---
https://hl7intl.art-decor.pub/ | Project index
Disclaimer
The content of this publication has been carefully prepared and reviewed. However, authors and contributors do not guarantee the accuracy, completeness or quality of the information provided, or that it is up-to-date. Liability claims against authors or contributors in respect of material or immaterial damage caused by the use or non-use of the information offered or by inaccurate or incomplete information are in principle ruled out provided that there is no provable culpable intent or gross negligence on author's or contributor's part. Authors / Contributors HL7 International - as author 2016-2024
List of Authors
Administrator Dr. Kai Heitmann Giorgio Cangioli Alexander Henket Catherine Chronaki Rob Hausam Dr. Stefan Sabutsch Stephen Chu François Macary Christof Gessner Andrea Fourquet Lori Fourquet

### Version Info

Date | By | Description
--- | --- | ---
2026‑02‑15 08:38:13 | Dr. Kai Heitmann | Official Release: 2.0.1 Changes applied so far from issues submitted for the 2.0.0-ballot.
| RESOLVED - NO CHANGE |
CDA-21167 | IPS Radiology Result Observation Component templateId issues updated | 2024-09-12
CDA-20071 | Alignment of the MMAT code cardinality between IPS and Pharma templates | 2021-09-29
CDA-2079 | STU-2079 – harmonization | 2021-09-23
| APPLIED |
CDA-21184 | Fix the "* to be checked ==>" links | 2026-01-27
CDA-21165 | Alerts Section & Patient Story Section templateId OIDs should follow convention | 2026-01-07
CDA-20545 | UV Generalized Medicine Class add required determinerCode | 2024-06-12
CDA-20037 | Change pharm:containerPackagedProduct determinerCode from INSTANCE to KIND | 2021-09-23
CDA-20541 | asContent.quantity extension: align template and XML schema | 2024-06-12
CDA-2083 | STU-2083 - generalizedMedicineClass | 2021-09-23
CDA-2084 | STU-2084 - substance administration | 2021-09-23
CDA-2081 | STU-2081 - containerpackagedProduct | 2021-09-23
CDA-2078 | STU-2078 - pharm:ingredient | 2021-09-23
CDA-2077 | STU-2077 - harmonize | 2021-10-20
CDA-2058 | STU-2058 - problem concern act | 2021-09-23
CDA-2059 | STU-2059 - problem concern act | 2021-09-23
CDA-2057 | STU-2057 - Pharm:ascontent.quantity | 2021-09-23
CDA-1979 | STU-1979 - Problem Status Observation | 2021-10-20
CDA-1975 | STU-1975 - languageCode element | 2021-09-23
CDA-1974 | STU-1974 - representedCustodianOrganization | 2021-09-23
CDA-1895 | STU-1895 - realmCode | 2021-09-23
CDA-1894 | STU-1894 - Manufacturedmaterial Example | 2021-09-23
CDA-1892 | STU-1892 - Finding day missing | 2021-09-23
CDA-1888 | STU-1888 - Cardinality change | 2021-09-23
CDA-1891 | STU-1891 - Ingredient Substance code and name optional | 2021-09-23
CDA-1887 | STU-1887 - Pregnancy status observation | 2021-09-23
CDA-1886 | STU-1886 - Value of code | 2021-09-23
CDA-1889 | STU-1889 - Procedure Date | 2021-09-23
2024‑11‑07 13:25:24 | Dr. Kai Heitmann | Official Release: 2.00 HL7 CDA® R2 Implementation Guide: International Patient Summary Edition 2 (Universal Realm), 1st STU Ballot, September 2024
2020‑07‑07 12:04:20 | Giorgio Cangioli | Official Release: v1.9.0 HL7 CDA® R2 Implementation Guide: International Patient Summary, Release 1 as used by IHE International Patient Summary (IPS) Profile Revision 1.1 – Trial Implementation
2018‑09‑06 09:52:42 | Giorgio Cangioli | Official Release: v1.86 There have been changes to the following 2 issues since the last intermediate version or release. Issue 142 "C-CDA Pregnancy Status alignment" with status "Open". Last event (2018-09-06T09:35:44): In the yesterday IPS call (2018-09-05) it was agreed to change the boolean value of the pregnacy status observation into a codeableConcept. The same shall be done in the next version of the CDA template. Issue 145 "Fix the Pregnancy section code" with status "Closed". Last event (2018-09-06T09:51:09): Pregnancy History Section updated
2018‑08‑29 11:43:19 | Giorgio Cangioli | Official Release: v1.85 Release: v1.85 STU Release after the reconciliation of the D2 Ballot for the January 2018 ballot cycle: HL7 CDA® R2 Implementation Guide: International Patient Summary, Release 1, STU There have been changes to the following 2 issues since the last intermediate version or release. Issue 143 "Procedure effectiveTime to 1..1 R" with status "Open". Last event (2018-07-12T10:53:27): Finding: the pr EN 17269 and the FHIR IPS procedure have a 1..1 Procedure date Suggestion: change the cardinality from 0..1 R to 1..1 R for alignment Further explanation: This should be added as STU comment as soon as the CDA IG will be published. Issue 144 "Pregnancy Status effectiveTime to 1..1 R" with status "Open". Last event (2018-07-12T11:16:18): Finding: the prEn 17269 indicates the Date of Observation as required (not mandatory) data. Suggestion: consider to change the cardinality from 0..1 R to 1..1 R Further explanation: -
2018‑07‑10 12:54:10 | Dr. Kai Heitmann | Official Release: v1.84 Check-Release towards STU after reconcile of the D2 Ballot for the January 2018 ballot cycle: HL7 CDA® R2 Implementation Guide: International Patient Summary, Release 1 There have been changes to the following 9 issues since the last intermediate version or release. Issue 61 "LOINC Code for the CertaintyObservation code" with status "Geschlossen". Letzte Ereignis (2018-03-19T10:02:42): According a conversation between Rob and Regenstrief, we should use 66455-7 Condition status. We agreed at the Paris March 2018 meeting. Issue 127 "Constrained template for the PlayingEntity" with status "Geschlossen". Letzte Ereignis (2018-02-08T16:54:31): Solved long ago.and published in the December ballot. Issue 136 "Ingredient Substance code and name both optional " with status "Offen". Letzte Ereignis (2018-02-07T15:52:12): Finding: Ingredient Substance code and name both are optional, which is probably not enough. HL7 Pharmacy WG and IHE have defined code O and name R. Suggestion: Make either name R or create a co-constraint code or name must be present Issue 137 "Update value set" with status "Geschlossen". Letzte Ereignis (2018-02-24T11:05:37): Updated! Issue 138 "ActStatusActiveCompleted no more used" with status "Offen". Letzte Ereignis (2018-02-24T11:59:08): Finding: The current guide does not use anymore this value set (the x_ActStatusActiveComplete is used instead) Suggestion: remove from the list ? Further explanation: already removed from the list reported in the CDA IG (wiki) - Issue 139 "Wrong datatype?" with status "Offen". Letzte Ereignis (2018-03-08T14:17:40): Unfortunately I had no time yet to update the data set with the latest CEN EN version.... this is for sure a typo, but several other changes have to be applied.. Issue 140 "Add body site to Medical Device (as entryRelationship)" with status "Offen". Letzte Ereignis (2018-03-19T17:49:56): Finding: The body site of the implant cannot be specified Suggestion: Add a body site as entryRelationship to an implant procedure carrying the body site Issue 141 "Move the code for binding for Absent or Unknown Devices" with status "Offen". Letzte Ereignis (2018-03-19T17:57:02): Finding: The code for Absent or Unknown Devices is placed now that the participation level code. Suggestion: Move the Absent or Unknown Devices code to the Supply.code (that have been dropped earlier but need to be re-introduced here) Further explanation: - Issue 142 "C-CDA Pregnancy Status alignment" with status "Offen". Letzte Ereignis (2018-05-14T14:57:50): Finding: StrucDoc today accepted a use case for "Possible Pregnant" that does not yet seem covered in HL7 IPS. Looking at C-CDA (code ASSERTION, value 77386006 (SNOMED CT), it looks as if there's more room for alignment than just this one use case. Suggestion: Seek alignment with C-CDA in general for this template, but at least consider "Possible Pregnant" as use case. Further explanation: Contact for C-CDA: Sarah Gaunt
2017‑12‑17 19:27:23 | Dr. Kai Heitmann | Official Release: v1.76 Release for the D2 Ballot for the January 2018 ballot cycle HL7 CDA® R2 Implementation Guide: International Patient Summary, Release 1 (PI ID: 1087) (CDAR2_INTLPATSUMMARY_R1_D2_2018JAN) There have been changes to the following 28 issues since the last intermediate version or release. Issue 19 "Allergy Agent Value Set" with status "Closed". Last event (2017-09-01T16:08:49): Issue 48 "IPS Comment Activity: schematron test assertion" with status "Closed". Last event (2017-11-22T18:27:07): Nothing to do Issue 50 "VS binding missing for methodCode and targetSiteCode" with status "Closed". Last event (2017-10-30T18:44:14): Decision taken during the 2017-10-11 call targetSiteCode: to be removed form Lab and Pathology results. (Giorgio to update the excel file). methodCode: to be removed results observations / procedure approachSiteCode: to be removed procedure targetSiteCode: intensional SCT based value set; preferred value set; not part of the request for free.for-use set… (all descendants of 442083009 |Anatomical or acquired body structure (body structure)) Issue 51 "result observation: full SCT binding" with status "Closed". Last event (2017-11-15T10:10:52): All the bindings issue related to the targetSiteCode; methodCode; and so on have been fixed. Issue 54 "Missing VSs for methodCode,approachSiteCode and targetSiteCode" with status "Closed". Last event (2017-10-30T18:44:36): Decision taken during the 2017-10-11 call targetSiteCode: to be removed form Lab and Pathology results. (Giorgio to update the excel file). methodCode: to be removed results observations / procedure approachSiteCode: to be removed procedure targetSiteCode: intensional SCT based value set; preferred value set; not part of the request for free.for-use set… (all descendants of 442083009 |Anatomical or acquired body structure (body structure)) Issue 55 "No value set for the procedure code" with status "Closed". Last event (2017-09-01T16:08:32): Intensional definition provided Issue 57 "Medical Device supply.code: value set binding missing" with status "Closed". Last event (2017-11-15T10:09:02): Call 2017-11-09 The supply code element has not been considered relevant for the purpose of the IPS. It has been omitted Issue 69 "Add ASSERTs for the defined constraints" with status "Open". Last event (2017-09-01T16:04:45): reported as ballot comment Issue 82 "Change the rule for language from nn-CC ?" with status "Closed". Last event (2017-12-12T19:02:11): Updated assertion Added the agreed constraint. Issue 84 "How remove the refrence to the human language value set ?" with status "Closed". Last event (2017-09-01T15:17:10): Removed. Not in the balloted PDF Issue 87 "Author functionCode missing value set" with status "Closed". Last event (2017-11-03T15:51:41): 2017-10-25 Do not assign a value set binding Issue 89 "assignedAuthor with no assignedPerson or assignedAuthoringDevice" with status "Closed". Last event (2017-11-03T15:13:07): According to the resolution of the ballot comment #203 at least one device or person shall be present. remove the conf "If assignedAuthor has an associated representedOrganization with no assignedPerson or assignedAuthoringDevice, then the value for "ClinicalDocument/author/assignedAuthor/id/@nullFlavor" SHALL be "NA" "Not applicable"" Issue 90 "Author code value set and description" with status "Closed". Last event (2017-11-03T15:39:23): According to the disposition agreed during the ballot the author code is valued with the professional roles (Doctors;...). (is the value set that was used for the functionCode) Issue 109 "Immunizations without immunoglobulins etc?" with status "Closed". Last event (2017-11-22T18:23:36): Call 2017-11-22 Keep the current value set Issue 110 "Missing Present x plus out of three plus" with status "Closed". Last event (2017-09-01T15:37:19): Issue 111 "64572001 Condition -> Disease" with status "Closed". Last event (2017-11-22T18:04:31): displayName fixed. the 404684003 Clinical finding (finding) can be used for conditions Issue 117 "Result Organizer with ObservationMedia?" with status "Closed". Last event (2017-08-21T10:15:45): The ObservationMedia is in the right place: Result Organizer. Same as in XD-LAB profile where it is part of the Battery Organizer and not part of the Laboratory Observation. APSR 2.0 also supports ObservationMedia within an Organizer: the Problem Organizer. Example of an electrophoresis: The Result Organizer contains as many observations as there are proteins fractions (albumin, alpha 1, alpha 2, ...), and contains one observationMedia, which provides the whole graph. Remember that the Result section contains zero to many Result organizers. This allows to group together a set of observations and the related images (observationMedia). Issue 121 "Value sets to be defined" with status "In Progress". Last event (2017-09-01T15:48:17): Microorganisms defined to be revised the Results Coded Values Pathology to be defined the IPS Results Coded Values Radiology Added as ballot comment the part related to radiology. Issue 122 "Visualization of union of VSs" with status "Closed". Last event (2017-09-01T15:45:41): When the rules are not too complex the intensional definition is shown in the main window Issue 125 "Check vocabulary and template flexibility" with status "Closed". Last event (2017-09-01T15:36:34): Issue 126 "Check choice items' representation" with status "In Progress". Last event (2017-09-01T15:38:45): Added as a ballot comment Issue 127 "Constrained template for the PlayingEntity" with status "In Progress". Last event (2017-08-21T09:09:02): Change requested as a comment to the ballot. Issue 130 "Examples to be revised (template IDs)" with status "Closed". Last event (2017-09-01T15:36:56): Issue 131 "Consider a revision of the name of the section" with status "Closed". Last event (2017-11-02T16:24:26): Call 2017-11-02 Align the name with the LOINC description Issue 132 "Remove cpm from the PQR elements" with status "Open". Last event (2017-09-06T15:14:53): The same change needs to be applied to the specifcation.... Issue 133 "change the cardinality of relatedDocument ?" with status "Open". Last event (2017-10-27T17:29:03) According to the CDA constraint "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. " Should we change the cardinality to 0..2 ? Issue 134 "Section/text is 0..1 M" with status "Closed". Last event (2017-11-23T22:17:59): Thanks for pointing to this, fixed to 1..1 M as it should be for all IPS Sections Issue 135 "Code missing" with status "Open". Last event (2017-11-27T19:41:39): d day is missing Add d
2017‑08‑02 13:30:41 | Dr. Kai Heitmann | Official Release: v0.95 Initial release for the HL7 ballot: HL7 CDA® R2 Implementation Guide: International Patient Summary, Release 1 (PI ID: 1087) (CDAR2_INTLPATSUMMARY_R1_D1_2017SEP ) There have been changes to the following 130 issues since the last intermediate version or release. Issue 1 "Undetermined / unknown agent" with status "Closed". See the issue for all details. Last event (2017-05-24T15:47:44): Two cases will e covered by this template known absent and unknown information. The value set and the templates have been updated for supporting this. Issue 2 "Not Known, unknown, undetermined adverse reaction" with status "Closed". See the issue for all details. Last event (2017-04-11T15:41:48): Solution identified and applied. See http://wiki.hl7.org/index.php?title=IPS_NoInfos_section Issue 3 "convert group to item" with status "Closed". See the issue for all details. Last event (2016-11-08T10:18:28): Oh I see, I simply mis-read your request, changed to item now. Issue 4 "Documentation of undetermined, unknown, not known cases" with status "Closed". See the issue for all details. Last event (2017-04-11T15:51:56): Those cases have been analyzed and a solution identified (see http://wiki.hl7.org/index.php?title=IPS_NoInfos_section). Issue 5 "Split type in two elements ?" with status "Closed". See the issue for all details. Last event (2016-11-15T15:02:46): Issue 6 "How to map kind of propensity" with status "Closed". See the issue for all details. Last event (2017-04-11T15:42:43): The kind of propensity is conveyed using the OBS.code see also http://wiki.hl7.org/index.php?title=IPS_problemObservation Issue 7 "How to document the parent Template IDs " with status "Closed". See the issue for all details. Last event (2016-11-15T08:58:44): No negative comments received Issue 8 "Medication entry : diversification of templates" with status "Closed". See the issue for all details. Last event (2017-02-21T15:44:02): Confirmed the idea of having only one template covering normal, tapered ,.. cases Issue 9 "SBADM effective time: IVL_TS or IVL_TS and TS" with status "Closed". See the issue for all details. Last event (2017-04-11T15:37:15): Solution identified (subordinate SBADM) and applied for the medication template entry Issue 10 "SBADM.code : clarification on their documentation" with status "Closed". See the issue for all details. Last event (2017-04-11T15:58:47): It should be "DRUG" or "IMMUNIZ"or a known absent / unknown code. Issue 11 "Relationships with potential parent templates" with status "Closed". See the issue for all details. Last event (2016-11-15T15:30:10): Finding: Based on the current choice about the documentation of "parent" templates (consider them as optional when applicable) what is the right type of relationships we need to use for them ? (derived, specialization, adaptations,..) for the time being adaptation has been used.... Call 25 Nov 2016 - use Adaptation this allow to include only optionally the parent templates - Further explanation: - Issue 12 "Textual Conformance Assertions" with status "Closed". See the issue for all details. Last event (2017-02-15T16:58:11): No negative comments have been received so far. To be reconsidered only if needed. Issue 13 "(Optional) Template version attribute" with status "Closed". See the issue for all details. Last event (2017-04-11T15:50:45): No needed for the time being Issue 14 "Value set id (as CDA extension)" with status "Open". See the issue for all details. Last event (2016-11-27T15:34:27): Issue 15 "Value for the ACT.code (Allergy Concern)" with status "Closed". See the issue for all details. Last event (2017-02-01T15:59:35): Change applied to the template Issue 16 "ValueSet for the statusCode (Allergy Concern)" with status "Closed". See the issue for all details. Last event (2017-04-11T15:33:43): The Concern statusCode is only active or completed. See the Paris meeting minutes. Issue 17 "effectiveTime cardinality (Allergy Concern)" with status "Cancelled". See the issue for all details. Last event (2016-12-06T16:40:11): It is required also for the IHE PCC Issue 18 "Check template ids for the allergy section" with status "Closed". See the issue for all details. Last event (2017-04-11T15:49:26): Decision to not refer any other potential parent template. See Paris Meeting Minute Issue 19 "Allergy Agent Value Set" with status "Feedback needed". See the issue for all details. Last event (2017-06-01T08:46:36): This one descendants of 373873005 |Pharmaceutical / biologic product (product)| containing > 1 "Has active ingredient" relationship sounds weird. Beyond the fact that I am unsure whether there is any term server that can handle that, what's the rationale? Issue 20 "Optionality of the entry text" with status "Closed". See the issue for all details. Last event (2017-02-03T17:10:04): Issue 21 "Optionality of the entryRelatiohsip(MFST) inversionInd" with status "Closed". See the issue for all details. Last event (2017-02-01T15:55:46): Template updated => attribute required Issue 22 "ID cardinality" with status "Closed". See the issue for all details. Last event (2017-01-11T15:25:18): call 20161221 cardinality 1...* Issue 23 "Usage of the observation code (and related value set )" with status "Closed". See the issue for all details. Last event (2017-04-11T15:43:08): See http://wiki.hl7.org/index.php?title=IPS_problemObservation Issue 24 "Value set for adverse reactions" with status "In Progress". See the issue for all details. Last event (2017-06-21T11:08:45): Suggested to consider a limited number of concpets (no more than 100 ?) look at the experience in Cataluna / Spain. Issue 25 "Representation of no data about medications" with status "Closed". See the issue for all details. Last event (2017-05-24T16:17:25): The way to represent this kind of infos has been defined. To be completed the process of adding the missing concepts to the SNOMED CT extension for HL7 International': this will be treated in a separate thread Issue 26 "cardinality of id (SBADM)" with status "Closed". See the issue for all details. Last event (2017-01-09T17:45:38): Issue 27 "SBADM status code" with status "Closed". See the issue for all details. Last event (2017-04-11T15:46:14): Statuscode limited to active and completed. See Paris Meeting Minutes Issue 28 "SBADM: datatype constrain for the second effectiveTime" with status "Closed". See the issue for all details. Last event (2017-04-11T15:38:37): There is no more second effective time. This information is povided in the subordinated SBADM.effective time. Datatypes have been identified and applied to the new template Issue 29 "ManufacturedProduct classCode" with status "Closed". See the issue for all details. Last event (2017-02-01T15:47:23): Change applied to the template Issue 30 "manufacturedMaterial optionality of @classCode and determinerCode" with status "Closed". See the issue for all details. Last event (2017-02-01T15:46:10): Template updated (optional attributes; if present fixed value) Issue 31 "Cardinality of MMAT.code and usage of originalText" with status "Closed". See the issue for all details. Last event (2017-04-11T15:40:53): MMAT.code left optional. Issue 32 "Certainty representation (for CDA templates)" with status "Closed". See the issue for all details. Last event (2017-04-11T15:36:21): certainty observation and used value set defined and included. Issue 33 "Missing codes (allergy type)" with status "Closed". See the issue for all details. Last event (2017-06-21T11:07:15): Considered closed. The management of the HL7 SNOMED Extensions is a distinct issue Issue 34 "Correct example" with status "Closed". See the issue for all details. Last event (2017-04-05T13:55:29): Issue 35 "LOINC Code for criticality" with status "Closed". See the issue for all details. Last event (2017-04-13T09:45:17): Finding: Identify/Request a LOINC code (or SNOMED ?) for criticality Suggestion: The LOINC code exists. Here it is: 82606-5 |Allergy or intolerance criticality| [ More detail on: https://s.details.loinc.org/LOINC/82606-5.html?sections=Simple ] Further explanation: - Issue 36 "Social History " with status "Closed". See the issue for all details. Last event (2017-07-12T17:03:32): Alcohol consumption and tobacco use tenplates have been added Issue 37 "Convert II.epsos" with status "Closed". See the issue for all details. Last event (2017-07-06T21:42:01): Done Issue 38 "Cardinality of the entry act IDs" with status "Closed". See the issue for all details. Last event (2017-07-18T10:36:02): Issue 39 "Specialized CD, CE, CV, datatypes" with status "Closed". See the issue for all details. Last event (2017-07-06T21:41:51): Introduced new datatypes: AD.IPS CD.IPS CE.IPS CV.IPS IVL_TS.IPS.TZ TEL.IPS TS.IPS.TZ Issue 40 "Cardinality of procedure entry" with status "Closed". See the issue for all details. Last event (2017-05-10T15:52:12): Reviewing minutes it was clear that procedure entries were required. Updated the template Issue 41 "Common data to be included for sections" with status "Closed". See the issue for all details. Last event (2017-05-24T15:24:30): All the sections have now author and informant Issue 42 "ietf3066 vs ietf5646" with status "Closed". See the issue for all details. Last event (2017-05-10T17:44:10): Issue 43 "Check BCP 47 OID" with status "In Progress". See the issue for all details. Last event (2017-05-10T17:42:10): Value set definition updated. To be checked if the OID used is correct. (for this reason the name of the issue has been updated) Issue 44 "Results organizer (and included obs) code binding" with status "Closed". See the issue for all details. Last event (2017-05-23T20:01:06): All the bindings have been added Issue 45 "Result Organizer: choices of OBSs ?" with status "Rejected". See the issue for all details. Last event (2017-05-24T15:49:17): Any combination seems to be allowed. No changes needed Issue 46 "Lab result description" with status "Closed". See the issue for all details. Last event (2017-05-24T17:19:54): Call May 24th: agreed to consider also the case of "pending" results Issue 47 "Check the Lab Obs statusCode " with status "Closed". See the issue for all details. Last event (2017-05-23T19:42:43): François: In a patient summary we need only "completed" and "active". An observation not performed or aborted or held … is of no interest to a patient summary. In most cases, only “completed” observations are of interest to the summary. In some rare cases, though, it may be useful to include also an "active" observation in the patient summary. Giorgio: updated all the status codes for result organizer and observations Issue 48 "IPS Comment Activity: schematron test assertion" with status "Open". See the issue for all details. Last event (2017-05-02T12:00:53): Not clear to me why the not(@value ) is checked since this attribute is required. And why the test is not simply not(starts-with(@value, ‘#’)). Thanks for explanations. Issue 49 "results observation: choice for the " with status "Closed". See the issue for all details. Last event (2017-06-07T16:30:53): included a choice for the observation.values Issue 50 "VS binding missing for methodCode and targetSiteCode" with status "Open". See the issue for all details. Last event (2017-05-02T12:15:14): Finding: Define and add a value set for the methodCode and targetSiteCode coded elements Suggestion: - Further explanation: - Issue 51 "result observation: full SCT binding" with status "Open". See the issue for all details. Last event (2017-05-02T12:27:24): Finding: for some of the used coded element : e.g. targetSiteCode.qualifier.value the full snomed ct is referenced. Is such a level of detail relevant for the IPS ? In case should we select a restricted value set for these elements ? is this correct in this context ? in case is this the way we'd like to adopt when a full code system is referenced (should we define a value set defined as the full snomed ct ?) the same applies to other element in this template and other related templates of the result section Suggestion: - Further explanation: - Issue 52 "Specimen hl7:performer to be defined" with status "Closed". See the issue for all details. Last event (2017-06-07T18:56:14): performer removed, examples cleaned, and descriptions refined, explaining what data is provided by this template and, which element carries each of these data Issue 53 "Specification of the type of specimen" with status "Closed". See the issue for all details. Last event (2017-06-07T19:01:45): Clarifications brought to the template, and example cleaned. Issue 54 "Missing VSs for methodCode,approachSiteCode and targetSiteCode" with status "Open". See the issue for all details. Last event (2017-05-02T13:15:46): Finding: No value sets have been defined for these elements. Suggestion: - Further explanation: - Issue 55 "No value set for the procedure code" with status "Feedback needed". See the issue for all details. Last event (2017-06-01T08:49:40): Did we not agree to start with the CORE Problem List Procedures http://art-decor.org/art-decor/decor-valuesets--hl7ips-?id=2.16.840.1.113883.11.22.6amp;effectiveDate=2017-02-01T00:00:00 for the ballot first? Issue 56 "entry text reference specification to be aligned" with status "In Progress". See the issue for all details. Last event (2017-05-02T16:58:40): Maybe we can think about a template fragment for all the texts to be included wherever appropriate... Issue 57 "Medical Device supply.code: value set binding missing" with status "Open". See the issue for all details. Last event (2017-05-02T15:36:16): Finding: No bindings have been defined for this element. should we omit the element ? Is this correct ? Should be added some description explaining how it should be used ? Suggestion: - Further explanation: - Issue 58 "Check Devices VS content" with status "In Progress". See the issue for all details. Last event (2017-06-21T15:06:50): Proposed on the previous call to use an intensional definition as all descendants of 40388003 |Implant, device (physical object) The expansion of this value set needs to be checked against the eHDSI value set currently listed in the value set. Update with the value set expansion .... Issue 59 "Immunization manufacturedMaterial.code value set missing" with status "Closed". See the issue for all details. Last event (2017-05-24T16:14:02): defined two new value sets (one for the unknown infos and one for the vaccines) added the binding Issue 60 "Add assert for the defined constraint" with status "Open". See the issue for all details. Last event (2017-05-02T18:16:17): Finding: add an assert for the constraint If the statusCode is completed this element is required Suggestion: - Further explanation: - Issue 61 "LOINC Code for the CertaintyObservation code" with status "Open". See the issue for all details. Last event (2017-05-11T09:57:27): (1) Check for a LOINC code (2) is the FHIR value set that should be used for the value ? (Suggestions received to use SCT) Issue 62 "rename VS" with status "Closed". See the issue for all details. Last event (2017-05-24T16:26:18): renamed Issue 63 "IPS condition status code to be defined" with status "Closed". See the issue for all details. Last event (2017-05-24T15:46:03): Updated the values set according to the data sent by Stephen Chu after the PC call of 23rd of may add a new value set for the allergy statuses created a new specialized template for handling this (allergy statuses observation) Issue 64 "Consider to add an assert for the constraint" with status "Open". See the issue for all details. Last event (2017-05-03T12:07:46): I was thinking about integrating the textual constraint with a check of the status reported in the [problem observation status].value. In order to avoid to have a status active and the effectiveTime.high valued... ..but with a low priority... Issue 65 "Clarify how to express intensional VSs" with status "Closed". See the issue for all details. Last event (2017-07-19T10:22:39): feature implemented for "simple" intensional definitions Issue 66 "Value set for substances to be specified" with status "Closed". See the issue for all details. Last event (2017-06-21T11:11:52): Issue 67 "Two templates for the problem status" with status "Closed". See the issue for all details. Last event (2017-05-03T10:07:43): They were actually the same template. Templates have been updated in order to use only one (the other has been cancelled) Issue 68 "Define the value set for hl7:routeCode" with status "Closed". See the issue for all details. Last event (2017-06-21T11:10:53): An intensional definition of the value set - based on EDQM - has been used. Issue 69 "Add ASSERTs for the defined constraints" with status "Open". See the issue for all details. Last event (2017-06-21T11:13:14): Issue 70 "Split the effectiveTime element with a choice" with status "Closed". See the issue for all details. Last event (2017-05-23T20:02:40): Choice added for differentiating the differtn data types Issue 71 "Add a choice for the doseQuantity" with status "Closed". See the issue for all details. Last event (2017-05-03T18:24:52): I think it is sufficient to have at least two examples for single quantity and range quantity. We handle that elsewhere in the same way and I don't see the need to really add a choice. Issue 72 "Add value set for event time" with status "Closed". See the issue for all details. Last event (2017-05-23T20:00:13): Added and bindings Issue 73 "Value set for doseQuantity and capacityQuantity unit" with status "In Progress". See the issue for all details. Last event (2017-05-19T16:55:43): Discussed in Madrid: clean up the UCUM based values sets (create a new issue) include a first set of examples of UCUM annotations from the Austrian value set allow for CWE (open) binding Issue 74 "Doseform value set to be reviewed" with status "Closed". See the issue for all details. Last event (2017-06-21T14:47:03): An intensional definition based on EDQM has been used Issue 75 "Package value set to be reviewed" with status "Closed". See the issue for all details. Last event (2017-06-21T11:13:29): Issue 76 "Quantity Units value set to be reviewed" with status "In Progress". See the issue for all details. Last event (2017-06-07T16:02:17): Use the Austrian value set as reference and cleaned up that content for the quantity purpose (with the other UCUM based value sets) add the revise value set in ART DECOR Issue 77 "Define Value sets for medicine strength" with status "In Progress". See the issue for all details. Last event (2017-05-10T16:52:05): Issue 78 "Define a value set for the active substances" with status "Closed". See the issue for all details. Last event (2017-06-21T11:12:44): Issue 79 "Harmonize the names of the value sets" with status "Open". See the issue for all details. Last event (2017-06-07T18:12:10): Issue 80 "Harmonize the names of the templates" with status "Open". See the issue for all details. Last event (2017-05-03T13:08:19): When all the templates are specified, harmonize as possible the unique and the display names of the templates Issue 81 "Is IPS ObservationMedia used ?" with status "Closed". See the issue for all details. Last event (2017-06-08T09:54:37): IPSObservationMedia is used by IPSResultOrganizer Issue 82 "Change the rule for language from nn-CC ?" with status "In Progress". See the issue for all details. Last event (2017-05-10T17:47:23): Issue 83 "Update the EDQM OID (Value Sets)" with status "Closed". See the issue for all details. Last event (2017-07-06T22:01:36): 998x done Issue 84 "How remove the refrence to the human language value set ?" with status "In Progress". See the issue for all details. Last event (2017-07-19T10:20:02): If the Value Set is no longer used in the project you can remove the reference to it by clicking on the delete X in the Value Set Bar in the viewer. Issue 85 "Check the condition verification statuses" with status "Closed". See the issue for all details. Last event (2017-06-21T11:15:47): Added unconfirmed according to the Stephen's mail of June 17th Issue 86 "Section description not aligned with the real structure" with status "Closed". See the issue for all details. Last event (2017-05-31T16:58:34): Description updated Issue 87 "Author functionCode missing value set" with status "Open". See the issue for all details. Last event (2017-06-12T14:19:05): Finding: No value set has been defined for the author/functionCode. Suggestion: - Further explanation: - Issue 88 "Add device author example" with status "Closed". See the issue for all details. Last event (2017-06-21T11:04:11): added Issue 89 "assignedAuthor with no assignedPerson or assignedAuthoringDevice" with status "Open". See the issue for all details. Last event (2017-06-12T17:30:37): Actually...this constraint is already there what we need to decide if if we'd like to add an assert that say if assignedPerson and assignedAuthoringDevice are missing the ClinicalDocument/author/assignedAuthor/id/@NullFlavor shall be "NA". (b) should in this case consider the opposite if it is "NA" the assignedPerson and assignedAuthoringDevice shall be omitted ? (c) should we add that in this case the representedOrganization shall be present ? Issue 90 "Author code value set and description" with status "Open". See the issue for all details. Last event (2017-06-12T14:32:22): Finding: Should we define a value set associated with the author.code ? should we add a description for this element ? Suggestion: - Further explanation: - Issue 91 "Other kinds of participants" with status "Closed". See the issue for all details. Last event (2017-06-21T11:29:33): Leave only the patient contact template. The contact may be a person or an organization. other kind of participation are covered by the openness of the template. Issue 92 "Rational for the use of concern act (allergy)" with status "Closed". See the issue for all details. Last event (2017-06-14T18:42:05): Based on the discussion made during the call of June 14th It has been agreed "Add a sentence that says that a concern may include more than one allergy conditions." Giorgio: Done Issue 93 "Rename the template (Allergies)" with status "Closed". See the issue for all details. Last event (2017-06-14T09:37:34): Great proposal, helps understanding, great action on changing the name. Issue 94 " No-drug substances revise defiinition" with status "Closed". See the issue for all details. Last event (2017-06-13T09:34:01): The definition has been updated Issue 95 "epSOSPersonalRelationship patient contact" with status "Closed". See the issue for all details. Last event (2017-07-18T10:38:29): The template has been maintained as patient contact, so there is no need to rename Issue 96 "Patient Contact : is the "choice" needed ?" with status "Closed". See the issue for all details. Last event (2017-06-21T11:27:08): changed applied Issue 97 "documentationOf code missing VS" with status "Closed". See the issue for all details. Last event (2017-06-21T18:32:45): omit the element Issue 98 "performer functionCode should be required ?" with status "Closed". See the issue for all details. Last event (2017-06-21T15:36:23): Changed as optional Issue 99 "Value set for the performer functionCode (epSOSHealthcareProfessionalRoles)" with status "Closed". See the issue for all details. Last event (2017-07-18T10:26:42): A new value set without the prefix epSOS has been created Issue 100 "OID for the ISCO code system" with status "Closed". See the issue for all details. Last event (2017-06-15T11:45:37): Leave as it is now, waiting for possible comments Issue 101 "Update the IPS OID root" with status "Closed". See the issue for all details. Last event (2017-07-06T22:02:32): All converted to: Templates 2.16.840.1.113883.10.22 / Value Sets 2.16.840.1.113883.11.22 Issue 102 "IPSBodyAuthor inclusion" with status "Closed". See the issue for all details. Last event (2017-06-15T11:10:39): Issue 103 "harmonize templates for the section level author" with status "Closed". See the issue for all details. Last event (2017-06-15T11:41:12): the IPSBodyAuthor template has been updated including also device author, all the section authors has been updated to the IPSBodyAuthor Issue 104 "Remove associated concepts in templates" with status "Closed". See the issue for all details. Last event (2017-06-14T18:47:26): All the temnplate mapping (should) have been removed Issue 105 "hl7:doseQuantity examples to be checked" with status "Open". See the issue for all details. Last event (2017-06-21T15:18:30): - revise the descriptions of the examples; - obtain from the Pharma group some exaples to be reported here Issue 106 "Subordinate SubstanceAdministration as separate template" with status "Closed". See the issue for all details. Last event (2017-06-15T14:35:17): Done Issue 107 "Should we limit the SocialHistory Types ? " with status "Closed". See the issue for all details. Last event (2017-07-12T17:04:30): Specialized Alcohol consumption and tobacco use templates have been added, so this issue is no more applicable (at least for this version of the template) Issue 108 "Check contextConductionInd (entry / sections)" with status "Closed". See the issue for all details. Last event (2017-07-19T10:23:50): Issue 109 "Immunizations without immunoglobulins etc?" with status "Open". See the issue for all details. Last event (2017-06-29T11:36:56): Finding: This value set does not include any Antiserum AND/OR toxoid or Immunoglobulin products. Is that the intention to explicitly exclude "immunisations" using immunoglobulins etc? Suggestion: Use descendants of 350326008 Vaccine, immunoglobulins and antisera (product) Issue 110 "Missing Present x plus out of three plus" with status "Feedback needed". See the issue for all details. Last event (2017-07-19T19:54:41): Done, created the actual value set Issue 111 "64572001 Condition -> Disease" with status "In Progress". See the issue for all details. Last event (2017-07-07T15:53:33): From todays call: Do we want to find a code that better reflects the original intention or do we stick with the code for disease? Issue 112 "282291009 Diagnosis interpretation (observable entity) " with status "Closed". See the issue for all details. Last event (2017-07-07T15:56:37): Corrected to 439401001 Diagnosis (observable entity) Issue 113 "Meaning of SCTID: 418799008 " with status "Closed". See the issue for all details. Last event (2017-07-07T15:54:11): Displayname corrected Issue 114 "Section LOINC code wrong" with status "Closed". See the issue for all details. Last event (2017-07-18T10:35:29): The section code has been updated Issue 115 "Why copy of usual comment templates" with status "Deferred". See the issue for all details. Last event (2017-07-12T18:46:14): There are actually THREE official Comment Entry Templates: 2.16.840.1.113883.10.20.1.40 Comment - in HL7 CCD 1.3.6.1.4.1.19376.1.5.3.1.4.2 IHE Comment Entry - in IHE PCC 2.16.840.1.113883.10.20.22.4.64 Comment Activity - in HL7 C-CDA and now ours 2.16.840.1.113883.10.22.4.22 IPS Comment Activity - in HL7 IPS It must appear as ridiculous to anybody outside (and hopefully also to us "insiders") if such an easy thing like a "comment activity" (entry) has three official live forms. Please also note that all of them carry the same semantics. However, we dicided today in the call to stay with our fourth live form to enforce consolidation. Issue 116 "Diagnosis is a observable entity" with status "Open". See the issue for all details. Last event (2017-07-07T15:48:49): Finding: 439401001 Diagnosis is a observable entity, we do not have it as a finding as the other items in the value set Issue 117 "Result Organizer with ObservationMedia?" with status "Open". See the issue for all details. Last event (2017-07-12T16:52:12): See also on this purpose issue#81 "Is IPS ObservationMedia used ?" https://art-decor.org/art-decor/decor-issues--hl7ips-?id=2.16.840.1.113883.3.1937.777.13.6.81 Issue 118 "Add title ?" with status "Closed". See the issue for all details. Last event (2017-07-18T12:20:15): Title added in the translation section Issue 119 "Add the translation section to the section templates" with status "Closed". See the issue for all details. Last event (2017-07-18T11:15:00): done Issue 120 "Intensional definition" with status "Closed". See the issue for all details. Last event (2017-07-20T14:42:54): I created proper intensional definitions for the following value sets: IPS Medical Devices hl7ips-valueset-23 Medicine Active Substances hl7ips-valueset-32 IPS No Drug Substances hl7ips-valueset-34 IPS Procedures hl7ips-valueset-35 IPS Vaccines hl7ips-valueset-44 As of now I am unable to express the intensional rules for the following value sets. I left the verbose definition: Medicine Route of Administration (EDQM) Medicine Doseform (EDQM) Medicine Package (EDQM) IPS Results Observation Radiology IPS Results Observation Laboratory IPS Multi-Ingredients Products Issue 121 "Value sets to be defined" with status "Open". See the issue for all details. Last event (2017-07-18T11:55:14): Finding: there is no definition for the : IPS Results Coded Values Pathology and IPS Results Coded Values Radiology IPS Results Microorganism value sets Suggestion: - Further explanation: - Issue 122 "Visualization of union of VSs" with status "Open". See the issue for all details. Last event (2017-07-19T10:21:01): Finding: When a value set is defined as an union of other value sets it would be nice if this information would be shown in the main window and not only as part of the textual description if provided. Suggestion: - Further explanation: - Issue 123 "Change proposals for LOINC" with status "Open". See the issue for all details. Last event (2017-07-19T10:32:59): Finding: I suggest to prepare a change proposal for LOINC to : - request a new code for certainty - revise the description of the (main) Patient Summary code (align with our definition) - revise the description for the Patient Summary unexpected care code. It should be a specialization of the previous one for human curated PSs. - request a new code for Patient Summary as specialization of the previous one for assembled PSs It would be nice if we could prepare a sections ontology for the PS (maybe after the publication...) Suggestion: - Further explanation: - Issue 124 "Check sections' flexibility" with status "Closed". See the issue for all details. Last event (2017-07-19T12:45:05): Updated all the flexibility to dynamic Issue 125 "Check vocabulary and template flexibility" with status "Feedback needed". See the issue for all details. Last event (2017-07-19T12:46:28): Revised all the used templates and harmonized the use of flexibility. to be reviewed Issue 126 "Check choice items' representation" with status "In Progress". See the issue for all details. Last event (2017-07-19T12:45:14): Choices of values in this context must be manually predicated, i.e. hl7:value[@xsi:type='PQ'] etc. In that context, the Schematron engine cannot guess what predicate to use, so it needs to added by hand. Issue 127 "Constrained template for the PlayingEntity" with status "Open". See the issue for all details. Last event (2017-07-19T12:43:16): Finding: for the specimen collection is generically contained the CDA PlayingEntity template. Suggestion: Consider to define a more specific template that will allow to define the vocabulry constraints when it is used for specimen collection Further explanation: - Issue 128 "Revise the template description " with status "Closed". See the issue for all details. Last event (2017-07-21T09:35:49): Issue 129 "Revise the template description" with status "Closed". See the issue for all details. Last event (2017-07-21T09:33:46): Decscription updated Issue 130 "Examples to be revised (template IDs)" with status "Feedback needed". See the issue for all details. Last event (2017-07-21T09:30:34): revised also the entry level templates..

Datasets, codes, OIDs and Rules: this information is used for rendering and validation purposes.