Difference between revisions of "IPS Appendix 1"
(Created page with "=Appendix= {{Responsible|NN}} ==Acronyms and abbreviations == ==Glossary == '''Compliance''': Compliance of one standard or specification is compliant with another standard o...") |
(→Validation artifacts) |
||
Line 29: | Line 29: | ||
==Validation artifacts == | ==Validation artifacts == | ||
You can test you specification against your implementation (instances). To download materials to your computer for local testing and validation consider... | You can test you specification against your implementation (instances). To download materials to your computer for local testing and validation consider... | ||
− | * ...the W3C schemas (actually valid for any CDA specification) located at the [[ | + | * ...the W3C schemas (actually valid for any CDA specification) located at the [[http://ips.art-decor.org Project Publication Pag]]. The actual release has a link to the XML materials as which the W3C schemas are part of; it also includes example CDA document instances. |
* ..the ISO schematron files to do validation locally by associating IPS CDA instances with the main schematron using an XML editor or to use the derived XSLT conversions and apply the according XSLT derivation to your local IPS CDA instance. | * ..the ISO schematron files to do validation locally by associating IPS CDA instances with the main schematron using an XML editor or to use the derived XSLT conversions and apply the according XSLT derivation to your local IPS CDA instance. | ||
Revision as of 15:41, 17 July 2017
Contents
Appendix
Acronyms and abbreviations
Glossary
Compliance: Compliance of one standard or specification is compliant with another standard or specification if all propositions true in the initial standard are also true in the complying standard. The target artifact is compliant with the source artifact if and only if all conformant implementations of the target are also conformant with the source. (RM-ODP). The term compliance is also used to state expectations as to how certain specifications need to satisfy possible legislative or regulatory constraints or requirements.
Conformance: Conformance relates an implementation to a standard. Any proposition that is true of the specification must be true in its implementation. (ISO, 2010).
Conformance Assessment: A process whereby a given implementation instance is evaluated to determine which f its various Conformance Assertions are valid implementations of a given specification’s Conformance Statements.
Conformance Statement : A conformance Statement is a statement that identifies testable requirements at a specified Conformance Point within a specification, explicitly defining the behavior which must be satisfied at these points. Conformance Statements will only occur in standard which are intended to constrain some feature of a real implementation, so that there exists, in principle, the possibility of testing.
Conformance assertion: Conformance assertion is a testable, verifiable statement made about a specific implementation instance against a corresponding Conformance Statement.
Conformance points: Conformance points are the evaluation of conformance at specific points in the implementation or specification. See Conformance.
Licenses
Following is a non-exhaustive list of third-party terminologies that may require a separate license:
- SNOMED CT: SNOMED International (formerly know as International Healthcare Terminology Standards Development Organization IHTSDO)[1] or info@ihtsdo.org
- Logical Observation Identifiers Names & Codes (LOINC): The Regenstrief Institute, Inc.
- Unified Code for Units of Measure (UCUM) : Regenstrief Institute, Inc. and the UCUM Organization
- International Classification of Diseases (ICD) : World Health Organization (WHO)
- EDQM Standard Terms : European Directorate for the Quality of Medicines & Healthcare (EDQM) [2]
Integrated examples
- links to example instances in the publication package
Validation artifacts
You can test you specification against your implementation (instances). To download materials to your computer for local testing and validation consider...
- ...the W3C schemas (actually valid for any CDA specification) located at the [Project Publication Pag]. The actual release has a link to the XML materials as which the W3C schemas are part of; it also includes example CDA document instances.
- ..the ISO schematron files to do validation locally by associating IPS CDA instances with the main schematron using an XML editor or to use the derived XSLT conversions and apply the according XSLT derivation to your local IPS CDA instance.
Operational information
- The IPS project has an official mailing list address ips(at)lists.hl7.org, hosted at the HL7 listserver. Visit your http://www.hl7.org/myhl7/managelistservs.cfm?ref=common at hl7.org and subscribe to the International Patient Summary (IPS) that is summarised under the Structured Documents Work Group.
- We also offer to write an email to info(at)international-patient-summary.net for inquiries regarding the specification
- The original specification is hosted on one of the ART-DECOR main servers, the project is reachable at the http://art-decor.org/art-decor/decor-project--hl7ips-.
- Any IPS specification release in HTML format resides at http://ips.art-decor.org. It is likely that the publication site will move to hl7.org permanently, we will inform about that process.
- The IPS specification on the wiki is hosted here (international-patient-summary.net). It is likely that the publication site will move to hl7.org permanently, we will inform about that process.
FAQ’s
This is a placeholder for future Frequently Askwed Quastions about the International Patient Summary.
How to reuse this template
- ↑ Get SNOMED CT http://www.ihtsdo.org/snomed-ct/get-snomed-ct
- ↑ EDQM Standard Terms https://standardterms.edqm.eu