-
# Description
The ability to export stories in a format supported by electronic health records (EHRs) and personal health records (PHRs) would enable users to:
* Share relevant information with …
-
The HL7 September Ballot includes the following ballot item "HL7 Cross Paradigm Implementation Guide: "Sex and Gender Representation, Release 1". This introduces v2 segments, FHIR extensions and CDA u…
-
I think the use of 'COFE Header' within the simplified comparison of CDA accreditation level 1 to FHIR Document Reference Level 1 may be very misleading to developers. I appreciate that a level 1 FHIR…
-
Can we formalize "definition of done" for each translation, and put it in this project wiki (https://github.com/FHIR/cda-examples-to-fhir/wiki)?
Are we translating CDA document as a whole, or by sect…
-
Für die Datenelemente (Abschnitt 4.2) sollte im Leitfaden eine Übersicht existieren, in der diese auf die jeweiligen Strukturen von CDA, FHIR und UKF gemappt sind.
Dies erhöht die Übersichtlichkeit f…
lhitc updated
6 years ago
-
## Problème observé
https://github.com/ansforge/IG-fhir-medicosocial-suivi-decisions-orientation/blame/f1f465b256135d221b79fd92b5613a15c1141184/input/pagecontent/index.md#L8
Balises mal gérées + t…
-
### Problem
Currently, we don't validate the outputs of our converter against the FHIR R4 schema. Generally things are well formed, but things like cardinality are not validated against the spec.
…
-
Will the Privacy Consent be moving to use of the FHIR Consent resource?
It is unclear to me what the function of the cda consent profile is. Is this a whole document, or a section? If whole document …
-
Should there be guidance that the FHIR Resource created or updated should include ANY and ALL original identifiers. For example a C-CDA entry level data can have an id, this id should be preserved in …
-
Hi,
We notice when we compared CDA and FHIR output for the same patient that there wasn't any ID or identifier linkage between the two.
Do you agree this is something that should be addressed?
We h…