Page Comparison

...

• Through CarePlan Update

  • Setting the CarePlan.careTeam

  • Setting the scheduled team changes in CarePlan.ehealth-teamschedule

  • Through CarePlan$update-care-teams

• Through EpisodeOfCare$update-care-teams (which also updates all CarePlan related to the EpisodeOfCare)

...

The Sharing Approval Policy of a ServiceRequest expresses wheter the whether the approval for registrering registering documents is automated or done manually. It is defined in ServiceRequest.ehealth-sharingApprovalPolicy.

...

• automatic - used when the approval of registering documents is wanted to be done automatically.

• manual - used when the approval of registrering registering documents should be done manually.

The inital initial ServiceRequest.ehealth-sharingApprovalPolicy is a copy from the ActivityDefinition, made at the time of creation.

...

The sharing Approval Policy is set using a conceptMap

The ConceptMap http://ehealth.sundhed.dk/ConceptMap/activitydefinition-code-to-perform-sharing is used to determine if the Sharing Approval Policy should be set based on the ServiceRequests code: http://ehealth.sundhed.dk/vs/activitydefinition-code

...

The column “Activitydefinition-code-to-perform-sharing” is used to decide wheter whether the Sharing Approval Policy should be set for the given activitydefinition code, by use of the ConceptMap.

...

...

Timing expression copied from PlanDefinition/ActivityDefinition created in KAM

If recurring timing expression is copied from PlanDefinition/ActivityDefinition created in KAM the following transformation is needed for the infrastructure to resolve the timing:

For periodUnit: WK and period greater than 1.

...

If PlanDefinition.action[].timingTiming.repeat.periodUnit is “WK” (Week) and PlanDefinition.action[].timingTiming.repeat.period is greater than 1. The following changes are needed for the expression to be resolvable in the infrastructure:

...

Timing expression copied from PlanDefinition/ActivityDefinition created in KAM

If recurring timing expression is copied from PlanDefinition/ActivityDefinition created in KAM the following transformation is needed for the infrastructure to resolve the timing:

For periodUnit wk (weekly)

...

If PlanDefinition.action[].timingTiming.repeat.periodUnit is wk (Week), apart from ServiceRequest.occurrenceTiming.repeat.boundsPeriod.start being mandatory, the following changes are required for the expression to be resolvable by the infrastructure:

Example

Expression from PlanDefinition.action[].timingTiming.repeat created in KAM. (Intention from KAM: Every second Monday at 10 AM, for 2 months)

...

Example

Expression from PlanDefinition.action[].timingTiming.repeat created in KAM. (Intention from KAM: Every second Monday at 10 AM, for 2 months)

"repeat": {
  "frequency": 1,
  "period": 2,
  "periodUnit": "wk",
  "dayOfWeek": [ "mon" ],
  "timeOfDay": [ "10:00:00" ],
  "boundsDuration": {
    "unit": "mo",
    "value": "2"
  }
}

Must be transformed to:

"repeat": {
  "frequency": 1,
  "period": 2,
  "periodUnit": "wk",
  "boundsPeriod": {
    "start": "2023-09-04T10:00:00.000+02:00" <-- Starting from a Monday at 10 AM
    "end": "2023-11-04T10:00:00.000+02:00" <-- ending after 2 months
  }
}

For periodUnit: other than WK(weekly)

...

• timeOfDay

  • timeOfDay is ignored for frequency-based timing but should be used to set ServiceRequest.occurrenceTiming.repeat.boundsPeriod.start

  • For clarity, it is advised to remove the value in timeOfDay as it is not used for frequency-based timing.

• boundsDuration

  • If “Angiv varighed” is filled out, boundsDuration should be used to set ServiceRequest.occurrenceTiming.repeat.boundsPeriod.end

  • boundsDuration must be removed

Expression from PlanDefinition.action[].timingTiming.repeat created in KAM. (Intention from KAM: Every third day at 10 AM, for 2 months)

...

"repeat": {
  "frequency": 1,
  

"

period": 2,
  

"periodUnit": "

wk",
  

"dayOfWeek": [ "mon" ],
  "timeOfDay": [ "10:00:00" ],
  "boundsPeriod": {
    "

start": 

"2023-09-01T08:00:00.000+02:00" <-- always required, can occur on any day of the week at any time of day
    

"

end": "

2023-11-01T08:00:00.000+02:00" <-- ending after 2 

months
  }

Must be transformed to:

}

For periodUnit other than wk (weekly)

...

...

Expression from PlanDefinition.action[].timingTiming.repeat created in KAM. (Intention from KAM: Every third day at 10 AM, for 2 months)

"repeat": {
        "duration": 2,
        "durationUnit": "h",
        "frequency": 1,
        "period": 3,
        "periodUnit": "d",
        "timeOfDay": [ "10:00:00" ],
        "boundsDuration": {
        "unit": "mo",
        "value": "2"
        }
      }

Must be transformed to:

"repeat": {
        "duration": 2,
        "durationUnit": "h",
        "frequency": 1,
        "period": 3,
        "periodUnit": "d",
        "boundsPeriod": {
          "start": "2023-08-28T10:00:00.000+02:00" <-- Starting from a Monday at 10 AM
          "end": "2023-10-28T10:00:00.000+02:00" <-- ending after 2 months
        }
}

...

"repeat": {
       "duration": 2,
        "durationUnit": "h",
        "frequency": 1,
        "

period": 

3,
        "

periodUnit": "

d",
        "

timeOfDay": [ "10:00:00" ],
        "

boundsPeriod": 

{
          "

start": "2023-08-28T06:00:00.000+02:00" <-- always required, can occur on any day of the week at any time of day
          "

end": "2023-

10-

28T06:00:00.000+02

:00" <-- ending after 2 months
        }
}

Managing offering ServiceRequest as extra activities

The extension includeAsExtra on ServiceRequest, is used to determine whether the ServiceRequest should be provided as an extra activity in the $get-patient-procedures result. The value for includeAsExtra is copied from the corresponding PlanDefinition.action during creation of the ServiceRequest ($apply operation), and the value can be updated on any individual ServiceRequest.

The value for includeAsExtra can be set through the TimingPicker. The default value for includeAsExtra is false when not scheduled or adhoc, and true when a schedule has been configured.

...

Maintaining ServiceRequest Status

...

...

• manual, a clinician must manually approve each submitted measurement for document registering

• automatic, the eHealth Infrastructure automatically creates the approval for document registering

If not set, the default behavior behaviour is manual.