GithubHelp home page GithubHelp logo

gematik / epa-xds-document Goto Github PK

View Code? Open in Web Editor NEW
3.0 13.0 1.0 2.34 MB

Resources for electronic health record, XDS Document Service for document and MIO related use cases.

License: Apache License 2.0

epa specification

epa-xds-document's Introduction


Electronic Health Record System (ePA XDS Document)

Table of Contents
  1. About ePA XDS Document
  2. Release Notes
  3. License
  4. Contributions
  5. Contact

About ePA XDS Document

This repository provides technical information for the Electronic Health Record (ePA) application as part of the Telematic Infrastructure (TI).

This branch relates to a particular release in context of ePA version 3 ('ePA für alle') The provided content comprises normative and supplementary resources for the XDS Document Service.

For resources related to ePA data management and basic services see further associated repositories: (follow links in Branchinformation.md)

  • ePA-Medication medication related resources
  • ePA-Basic Basic services related resources

The current branch accompanies a particular release of specification documents of ePA version 3 (a set of normative specification documents for components, product types and vendor types) published on Fachportal Gematik (see Branchinformation.md for specific version information and links). The content in /src is normative in context of requirements defined by those specification documents and is essential for product approvals. Any other content is for information. Normative content here, the associated repositories and the documents together form a single product release of the Electronic Health Record system for an approval process. The affected and covered product types are ePA-Aktensystem and ePA-Frontend des Versicherten.

Release Notes

See ReleaseNotes.md for all information regarding the releases.

License

Copyright 2024 gematik GmbH

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.

See the LICENSE for the specific language governing permissions and limitations under the License.

Unless required by applicable law the software is provided "as is" without warranty of any kind, either express or implied, including, but not limited to, the warranties of fitness for a particular purpose, merchantability, and/or non-infringement. The authors or copyright holders shall not be liable in any manner whatsoever for any damages or other claims arising from, out of or in connection with the software or the use or other dealings with the software, whether in an action of contract, tort, or otherwise.

The software is the result of research and development activities, therefore not necessarily quality assured and without the character of a liable product. For this reason, gematik does not provide any support or other user assistance (unless otherwise stated in individual cases and without justification of a legal obligation). Furthermore, there is no claim to further development and adaptation of the results to a more current state of the art.

gematik may remove published results temporarily or permanently from the place of publication at any time without prior notice or justification.

Contributions

This repository is for publication of approved artefacts in context of a specific ePA release. Changes to normative content may be applied in rare exceptional cases but is not intended. Such changes will be covered by follow-up releases in different branches. Therefor submission of issues and pull requests are not rejected by default but the preferred channel is a contact via gematik website (see Contact below)

Contact

Please use the contact sheet https://fachportal.gematik.de/kontaktformular and choose "elektronische Patientenakte (ePA)" as request category in drop-down list "Thema der Anfrage/Kategorien".

epa-xds-document's People

Contributors

gematik-entwicklung avatar gematik1 avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

alisianoi

epa-xds-document's Issues

Versionsübergreifende Typisierung von Dokumenten

Ich vermisse in den Spezifikationen eine Codeliste für die versionsübergreifende Typisierung der hier in den IGs referenzierten "feingranularen" Dokumenttypen etwa auf der logischen Ebene eines KDL Codes. Ein solcher Code sollte wohl angelehnt an KDL spezifiziert werden, oder besser noch in Zusammenarbeit mit DVMD als Teil der KDL angelegt werden.

Die IGs enthalten lediglich versionsabhängige "technische" Identifier (u. a. in formatCode oder in einigen Fällen als canonicalUrl). Eine einheitliche versionsübergreifende Bezugnahme auf den Dokumenttyp ist damit nicht möglich, es wird jedenfalls keine Vorgehensweise dafür spezifiziert.

Klärungsbedarf besteht m. E. dazu, wie in den ePA-Anwendungen mit Dokumenten umzugehen ist, für die es sowohl strukturierte (FHIR, CDA) als auch unstrukturierte (PDF, JPG) Ausprägungen in einer ePA gibt oder geben kann. Eine Abstimmung mit DVMD (und Anwendern der gematik-Spezifikationen) zum Zusammenspiel mit KDL erscheint mir wünschenswert.

WSDL 1.1 Binding for SOAP 1.2 minOccurs=0

Hi,

WSDL 1.1 Binding Extension for SOAP 1.2

/wsoap12:header/@{any}
This is an extensibility mechanism to allow additional attributes, defined in a foreign namespace, to be added to the element.

Is the intention really to add minOccurs="0" from the XML namespace(?) to the SOAP header in the WSDL document?
This causes some difficulties for some parsers and class generators.

<soap12:header message="ihe:Header_Message" part="headerPart" use="literal" minOccurs="0"/>

<soap12:header message="ihe:Header_Message" part="headerPart" use="literal" minOccurs="0"/>

best regards

Einheitliche Strukturen in den IGs - auch für mimeType

https://github.com/gematik/ePA-XDS-Document/blob/ed6441767d7081d8d680704e225465085c017d1d/src/implementation_guides/ig-schema-definition.json#L96C1-L103C1

Ich schlage vor, die Codes für mimeTypes wie alle anderen CodeSystems in den IGs zu behandeln. Auch für die mimeTypes sollte die Angabe in der Form code, codeSystem und optional displayName erfolgen, wie bei allen anderen Metadaten-Slots in den IGs.

Ein Beispiel (aus der Schweiz) für die praktische Umsetzung findet sich hier:
https://fhir.ch/ig/ch-epr-term/ValueSet-DocumentEntry.mimeType.html

Der vorgeschlagene Identifier "urn:ietf:bcp:13" für das codeSystem verweist auf die RFC-Spezifikation BCP 13 ( https://www.rfc-editor.org/info/bcp13 ) und wird auch in der internationalen FHIR-Spezifikation angegeben:
siehe https://www.hl7.org/fhir/R5/valueset-mimetypes.html

Dies würde die softwareseitige Nutzung und Weiterverarbeitung der gematik IGs vereinfachen und vereinheitlichen.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.