Adjustment and Import of Plan Templates
- Erik Nielsen
- Mikkel Mahler
- Roxana Manea
As of eHealth Infrastructure Release 2024.3, the Clinical Administrative Application provides the ability to export and import plan templates.
A clinical administrative user may need to export and import plan templates to another eHealth environment.
The user can export and import plan templates using the Clinical Administration Application (KAM in Danish). After the import the imported plan templates may need some adjustments.
This using the standard service request described on this page the service desk can perform some of these adjustments.
Possible adjustments could be:
replacement of publisher - a plan template exported from a test environment or education environment may refer to a questionnaire with a publisher reflecting a test user.
re-identification of municipal organizations - a plan template exported from a test environment or education environment may contain parts (PlanDefinition, ActivityDefinition, Questionnaire etc.) referring to one or more municipal FHIR Organization originating from FK Organisation (see Managing and Using Organization, CareTeam and Practitioner | Origin and Use of Organization). The municipal FHIR Organization originating from the FK Organisation does not have the same identifier on test and production environments. As a consequence, the manual import of plan templates with parts referring to municipal FHIR Organization originating from FK Organisation will fail. If the municipal FHIR Organization does not originate from the FK Organization, you just have to check that the identifier matches the one on the target (Prod) environment. If they do, importing should be safe.
Required Input from Requester
The following input is required per plan template (PlanDefinition):
Input Element (down) | Required or optional | Example | Comment |
|---|---|---|---|
PlanDefinition title (citizen directed) | Required | Telma KOL plan 2023 | This is “Borgervendt navn” (Citizen directed name) as shown for a plan template in the Clinical Administrative Module (Da: Klinisk Administrative Modul shortened KAM) |
PlanDefinition employee title | Required | Telma KOL plan 2023 | This is “Medarbejdervendt navn” (Employee directed name) as shown for a plan template in KAM |
PlanDefinition version | Required | 3.4 | This is the business version of the plan template as shown as “Version” in KAM. |
Source Environment | Required | EXTTEST |
|
Destination Environment | Required | PROD |
|
Publisher Pairs | Optional (but required if a Questionnaire is part of PlanDefinition’s activities) |
| In the Questionnaire Editor in KAM, this is shown as “Udgiver” (Publisher) for a questionnaire. |
Municipal Organization Name and Identifier Pairs | Optional (but required if municipal organizations are referred and PROD is involved as either Source or Destination Environment) |
| The Source Identifier is Copenhagen Municipality’s UUID in EXTTEST. The Destination Identifier is Copenhagen Municipality’s UUID in PROD. |
Request Outcome
As part of processing the request, validation of completeness of input data is performed.
Validation errors are returned in case:
Incomplete Publisher Pairs - At least one entry in Publisher Pairs is provided in input but exported PlanDefinition(s) and referred resources from the Source Environment contain Publisher for which no entry of pair has been provided.
Incomplete Municipal Organization Name and Identifier Pairs - PROD is either Source or Destination Environment and at least on entry in Municipal Organization Name and Identifier Pairs is provided in input but exported PlanDefinition(s) and referred resources from the Source Environment contain a reference to Municipal Organization for which no entry of pair has been provided.
The expected outcome is that the PlanDefinition(s) have been imported to the Destination Environment, and adjusted as per input.