...
The eHealth Infrastructure carries the coexistence tag to automatically created create resources and as a convenience where applicable. This enables certain searches with coexistence tags and helps minimizing minimise the burden of marking up resources, respectively.
Resource Types to Mark Up with Coexistence Tag | Resource Types to Conditionally Mark Up with Coexistence Tag | Resource Types Automatically Marked Up with Coexistence Tag | Resource Types not to Mark Up with Coexistence Tag |
|---|---|---|---|
EpisodeOfCare | Appointment | CarePlan, ServiceRequest | ValueSet, CodeSystem, NamingSystem, ConceptMap |
Communication (ehealth-message) | Observation, QuestionnaireResponse, Media | Organization, CareTeam, Practitioner, PractitionerRole | |
Consent, Provenance | Goal | PlanDefintition, ActivityDefinition, DocumentReference | |
Device, DeviceMetric | Communication (ehealth-communication) for annotations | Library | |
ClinicalImpression, Task | Questionnaire, View, ActionGuidance | ||
DeviceUseStatement | Patient, RelatedPerson |
| Info |
|---|
In Release 12, there is no automatic carrying of coexistence tag for:
A workaround is for solutions to perform mark up with their coexistence tag in these cases. |
...
it is short
it does not indicate whether used for a solution or solution complex
it carries no value indicating the solution/solution complex’s product name, vendor or version
Acquiring a source
...
URI
The source uri URI identifies which solution created a given resource. Contact the eHealth Infrastructure system administration to obtain a value.
...
is short
does not indicate the solution/solution complex’s product name, vendor or version
Marking up resources with a coexistence tag
When creating a FHIR resource, add your coexistence tag to the FHIR resource element meta.tag. The tag element is a Coding so a coexistence tag value must be added as:
...
At the same time, add the source uri URI to:
.meta.source=urn:dk:ehealth:<value>
Deciding on conditional markup with a coexistence tag
As apparent from the table above, there are resources where markup with a coexistence tag is conditional. In general, if any of these resources are either referencing a coexistence-tagged resource, the tag should be copied (carried) by the client/solution system.
...
For instance, searching for EpisodeOfCare resources created for one’s own system with coexistence tag value xa:
...
Multiple coexistence tags can be added and separated with a comma:
GET <base url>/fhir/EpisodeOfCare/?subject=<some Patient reference>&_tag=http://ehealth.sundhed.dk/cs/ehealth-system|xa,http://ehealth.sundhed.dk/cs/ehealth-system|xb
...
In automated processing in the eHealth infrastructure
rule execution
coexistence tag from EpisodeOfCare/CarePlan/ServiceRequest is carried to rule-controlled creation of ClinicalImpression and/or Task and/or ehealth-message profile Communication
missing measurements check
coexistence tag from EpisodeOfCare/CarePlan/ServiceRequest is carried to ehealth-message Communication about measurements missing
reminder about upcoming measurement measurements to the Patient
coexistence tag from EpisodeOfCare/CarePlan/ServiceRequest is carried to ehealth-message Communication about the reminder
scheduled changes in EpisodeOfCare/CarePlan status and/or list of associated CareTeam
coexistence tag from EpisodeOfCare/CarePlan/ServiceRequest is carried to ehealth-message Communication about the change
On $create-episode-of-care (https://docs.ehealth.sundhed.dk/latest-released/ig/OperationDefinition--s-create-episode-of-care.html)
coexistence tag from EpisodeOfCare is carried to ehealth-message Communication about the creation
On $apply (https://docs.ehealth.sundhed.dk/latest-released/ig/OperationDefinition-PlanDefinition-i-apply.html)
coexistence tag from EpisodeOfCare is carried to ehealth-message Communication, CarePlan, and ServiceRequest
On $submit-measurement (https://docs.ehealth.sundhed.dk/latest-released/ig/OperationDefinition--s-submit-measurement.html)
coexistence tag from ServiceRequest is carried to Observation, QuestionnaireResponse, Media and Provenance
On creation of:
DeviceUseStatement
coexistence tag from CarePlan is carried to DeviceUseStatement
...