From ebec5b7596c6b63fc9ba32033297a3bcd0149789 Mon Sep 17 00:00:00 2001 From: John DAmore Date: Wed, 16 Oct 2024 10:04:36 -0400 Subject: [PATCH] FHIR-47491 quotes and remove 17269, change link --- input/fsh/profiles/BundleUvIps.fsh | 2 +- input/fsh/profiles/CompositionUvIps.fsh | 4 ++-- .../Known-Issues-and-Future-Development.md | 2 +- input/pagecontent/index.md | 12 ++++++------ 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/input/fsh/profiles/BundleUvIps.fsh b/input/fsh/profiles/BundleUvIps.fsh index fe15e318..e4a900c0 100644 --- a/input/fsh/profiles/BundleUvIps.fsh +++ b/input/fsh/profiles/BundleUvIps.fsh @@ -9,7 +9,7 @@ Description: "This profile represents the constraints applied to the Bundle reso * ^contact.telecom.system = #url * ^contact.telecom.value = "http://www.hl7.org/Special/committees/patientcare" * ^jurisdiction = $m49.htm#001 -* ^purpose = "An International Patient Summary (IPS) bundle is an electronic health record extract containing essential healthcare information about a subject of care, comprising at least the required elements of the IPS dataset. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country." +* ^purpose = "An International Patient Summary (IPS) bundle is an electronic health record extract containing essential healthcare information about a subject of care, comprising at least the required elements of the IPS dataset. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country." * obeys bdl-ips-1 * . ^short = "International Patient Summary Bundle" * . ^definition = "International Patient Summary Bundle. \r\nA container for a collection of resources in the patient summary document." diff --git a/input/fsh/profiles/CompositionUvIps.fsh b/input/fsh/profiles/CompositionUvIps.fsh index f93440a9..a6aaafab 100644 --- a/input/fsh/profiles/CompositionUvIps.fsh +++ b/input/fsh/profiles/CompositionUvIps.fsh @@ -4,7 +4,7 @@ Id: Composition-uv-ips Title: "Composition (IPS)" Description: """Clinical document used to represent the International Patient Summary (IPS) data set. An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care. -The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country. +The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country. """ * ^version = "1.1.0" * ^status = #active @@ -13,7 +13,7 @@ The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition- * ^contact.telecom.system = #url * ^contact.telecom.value = "http://www.hl7.org/Special/committees/patientcare" * ^jurisdiction = $m49.htm#001 -* ^purpose = "An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care, comprising at least the required elements of the IPS dataset. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in EN 17269 and ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country." +* ^purpose = "An International Patient Summary (IPS) document is an electronic health record extract containing essential healthcare information about a subject of care, comprising at least the required elements of the IPS dataset. The IPS dataset is minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant. As specified in ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country." * ^copyright = "HL7 International" * . ^short = "International Patient Summary composition" * . ^definition = "International Patient Summary composition. \r\nA composition is a set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. \r\nWhile a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained." diff --git a/input/pagecontent/Known-Issues-and-Future-Development.md b/input/pagecontent/Known-Issues-and-Future-Development.md index 50c5b22c..393896ca 100644 --- a/input/pagecontent/Known-Issues-and-Future-Development.md +++ b/input/pagecontent/Known-Issues-and-Future-Development.md @@ -1,5 +1,5 @@ ### Known Issues -1. Lack in representation of the summarization activities, including who did it, what was done (medication reconciliation, allergy reconciliation, medication allergy reconciliation, immunization/vaccination reconciliation, problem list/diagnosis reconciliation), what was the result, when and where was it done. This covers also the "Nature of the IPS" element included in EN 17269 and ISO 27269. +1. Lack in representation of the summarization activities, including who did it, what was done (medication reconciliation, allergy reconciliation, medication allergy reconciliation, immunization/vaccination reconciliation, problem list/diagnosis reconciliation), what was the result, when and where was it done. This covers also the "Nature of the IPS" element included in ISO 27269. 1. Profile specificity to be improved. Not all the expected rules can be automatically validated, due to a lack of representation in the specified profiles. 1. All of the slicing rules defined for the section entries have been specified in this version as open. This choice has been made to give more flexibility to the IPS, at the expense of the capability of fully and automatically validating the instances. In this sense the profile may technically allow the inclusion of inappropriate resources. Specifiers are encouraged to add further constraints or additional slices to mitigate this risk. Future versions may reconsider the current choice. 1. More constrained vocabularies. The choices made in this version reflect the need of balancing the expectations of reducing optionality, to improve interoperability; and of avoiding over-constraints, to facilitate the local adoption. Moreover, it has been recognized the current lack, in some cases, of globally recognized and freely usable vocabularies (e.g. for the identification of medications); and the need, for specific concept domains, to extend the value sets based on new SNOMED CT and SNOMED IPS Terminology content. For these reasons, the binding is required only in a few cases; preferred or extensible bindings have been used instead. diff --git a/input/pagecontent/index.md b/input/pagecontent/index.md index b7cc059f..bac39409 100644 --- a/input/pagecontent/index.md +++ b/input/pagecontent/index.md @@ -1,5 +1,5 @@ An **International Patient Summary (IPS) document** is an electronic health record extract containing essential healthcare information about a subject of care. -As specified in EN 17269 and ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. +As specified in ISO 27269, it is designed for supporting the use case scenario for ‘unplanned, cross border care’, but it is not limited to it. It is intended to be international, i.e., to provide generic solutions for global application beyond a particular region or country. The IPS dataset is **minimal and non-exhaustive; specialty-agnostic and condition-independent; but still clinically relevant**. @@ -17,15 +17,15 @@ The initial focus of the International Patient Summary (IPS) was the unplanned c ### Project Background -Details on the project background are available in the IPS Website. +Details on the project background are available in the IPS Website. ### Project Scope -As specified in EN 17269 and ISO 27269, the IPS dataset is a "minimal, non-exhaustive set of data elements required for the international patient summary". A Patient Summary is defined by ISO/TR 12773-1:2009 as a "Health record extract comprising a standardized collection of clinical and contextual information (retrospective, concurrent, prospective) that provides a snapshot in time of a subject of care’s health information and healthcare." +As specified in ISO 27269, the IPS dataset is a "minimal, non-exhaustive set of data elements required for the international patient summary". A Patient Summary is defined by ISO/TR 12773-1:2009 as a "Health record extract comprising a standardized collection of clinical and contextual information (retrospective, concurrent, prospective) that provides a snapshot in time of a subject of care’s health information and healthcare." -‘Minimal’ reflects the ideas of ‘summary’ and the need to be concise, but also alludes to the existence of a core set of data elements that all health care professionals can use; it is intended to be a speciality agnostic and condition independent set. It does not imply that all the items in the data set will be used in every summary. It is also possible to refine the extract from a record such that the content of the summary is more relevant to a particular condition (e.g. asthma) but no asthma-specific elements will be specified in this standard. -The IPS Document or IPS can be extended by non-IPS standard condition-specific data. -‘Non-exhaustive’ recognizes that the ideal data set is not closed, and is likely to be extended, not just in terms of requirement evolution, but also pragmatically in instances of use. [EN 17269; ISO 27269]. +As a further definition of terms in ISO 27269, "'Minimal' reflects the ideas of 'summary' and the need to be concise, but also alludes to the existence of a core set of data elements that all health care professionals can use; it is intended to be a speciality agnostic and condition independent set. It does not imply that all the items in the data set will be used in every summary. It is also possible to refine the extract from a record such that the content of the summary is more relevant to a particular condition (e.g. asthma) but no asthma-specific elements will be specified in this standard. The IPS Document or IPS can be extended by non-IPS standard condition-specific data. + +'Non-exhaustive' recognizes that the ideal data set is not closed, and is likely to be extended, not just in terms of requirement evolution, but also pragmatically in instances of use." Furthermore the scope of the IPS is global. Although this is a major challenge, this implementation guide takes various experiences and newer developments (e.g. US Core Implementation Guide (FHIR IG)) into account to address, as far as possible, global feasibility.