The eHealth Infrastructure provides a mechanism for solutions to co-exist despite not being aligned on all processes and resources used. Coexistence (in Danish: Sameksistens) is a softened form of multitenancy where the solutions choose when to search generically or specifically.
The general idea is that each solution or solution complex:
is assigned a coexistence tag
performs markup with the coexistence tag when creating resources
decides when to use the coexistence tag in searches
The eHealth Infrastructure carries the coexistence tag to automatically created resources and as a convenience where applicable. This enables certain searches with coexistence tags and helps minimizing 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 | |
Communication (ehealth-communication) for annotations | |||
Device, DeviceMetric | ClinicalImpression, Task | Questionnaire, Library, View, ActionGuidance | |
DeviceUseStatement | Patient, RelatedPerson |
In Release 12, there is no automatic carrying of coexistence tag for:
creation of Goal
solution-initiated creation of ClinicalImpression and Task
creation of Communication (ehealth-communication)
A workaround is for solutions to perform mark up with their coexistence tag in these cases.