Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hg-CorrespondenceItem #29

Open
wants to merge 7 commits into
base: develop-profiles
Choose a base branch
from

Conversation

niekvangalen
Copy link

@niekvangalen niekvangalen commented Mar 4, 2024

Profiel voor het concept "Correspondentie-item" zoals in de dataset gedefinieerd onder "Dossiergegevens".

@NictizEduard NictizEduard removed their assignment Oct 10, 2024
<use value="work" />
</telecom>
</contact>
<description value="An CorrespondenceItem as used within the medical record (Dossiergegevens) section in the ELZ data set. It is based on the HL7 FHIR Communcation core 4.0.1 resource as much as possible, but adds some elements that are necessary for data exchange in the primary care domain." />
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spelfout HL7 FHIR Communication

<comment value="IdentificationNumber" />
</mapping>
</element>
<element id="Communication.basedOn">
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing short RelationEpisodeOfCare, alias RelatieZorgepisode and definition. English name and definition in ART-DECOR should be added as well.

<mapping>
<identity value="hg-dataset-020-beta1-20230612" />
<map value="hg-dataelement-1288" />
<comment value="EpisodeOfCare" />
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RelationEpisodeOfCare

</element>
<element id="Communication.basedOn">
<path value="Communication.basedOn" />
<mapping>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing target nl-core EpisodeOfCare profile

@@ -0,0 +1,130 @@
<?xml version="1.0" encoding="utf-8"?>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing short, alias and definition for every mapped element

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Targetprofiles for nl-core are missing

<type value="DocumentReference" />
<baseDefinition value="http://hl7.org/fhir/StructureDefinition/DocumentReference" />
<derivation value="constraint" />
<differential>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing mapping dataelement 374, alias, short, definition.

</element>
<element id="Communication.note.author[x]">
<path value="Communication.note.author[x]" />
<mapping>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The author of the message is not the author of the note. I think this should be mapped somewhere else. Same for CorrespondenceProcessingDate.

<targetProfile value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport" />
<targetProfile value="http://hl7.org/fhir/StructureDefinition/DocumentReference" />
</type>
<mapping>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is reasonReference the correct element or should it be payload.contentReference?

<mapping>
<identity value="hg-dataset-020-beta1-20230612" />
<map value="hg-dataelement-381" />
<comment value="CorrespondenceSummary" />
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be mapped on payload.contentString or DocumentReference.description?

@@ -0,0 +1,66 @@
<?xml version="1.0" encoding="utf-8"?>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing mapping of DocumentVersienummer (376)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants