Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

The non Patient specific PlanDefinition likely references a number of ActivityDefinition defining what activities in what order constitute the plan, possibly with default measurement ranges. On applying a PlanDefinition, Patient specific counterparts to the PlanDefinition and ActivityDefinition resources are created as CarePlan and ServiceRequest resources, respectively.

Gliffy
imageAttachmentIdatt1717436591
macroId4d72224f-dbdf-444e-ad4f-63e7d11825f1
baseUrlhttps://ehealth-dk.atlassian.net/wiki
namePatient specific plans and activities with definitions in Administrative Domain
diagramAttachmentIdatt1717403811
containerId1661141027
timestamp1618313365923

...

Finding The Appropriate PlanDefinition

...

...

At some point before a ServiceRequest has status set to active, its measurement regime must be defined with a starting date/time.

Note

It is expected that a Telemedicine Solution intended for employees guides the user in setting starting date/time for ServiceRequest even when initially set with status on-hold (as is the case for ServiceRequest referencing ActivityDefinition with trigger dependency expressed in PlanDefinition).

Note

It is expected that a Telemedicine Solution in some form provides information about the intended time-wise layout of activities captured in the PlanDefinition and ActivityDefinition resources which the citizen’s plan is based on. This includes intention captured in:

  • PlanDefinition.action.timing[x] (which is copied to ServiceRequest.occurrence[x] initially, if present)

  • PlanDefinition.action.relatedAction (actionId, relationship and possible offset[x])

  • ActivityDefinition.timing[x] in ActivityDefinition referenced from ServiceRequest.instantiatesCanonical - This timing could specify a duration.