Versions Compared

Old Version 16

changes.mady.by.user Erik Nielsen

Saved on

compared with

New Version 17

changes.mady.by.user Erik Nielsen

Saved on

Key

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

...

Note

It is expected that a Solution or Telemedicine Solution component detects whether measuring is performed automatically or by manual entry and examines whether corresponding ActivityDefinition.relatedArtifact (as defined above) is present. If so, the Telemedicine Solution or Solution component is expected to display the text and/or picture to the user.

Presenting Offsets between Activities and Duration of Activity

Offset between activities has different meaning depending on where used. The citizen’s CarePlan refers a PlanDefinition in which offset can be defined between its comprised activities through PlanDefinition.action.relatedAction.offset. In the following, it is assumed that the Patient-specific adjustments of measurement regimes (in ServiceRequest.timing) have not veered off significantly from the intention for offset and/or measurement regimes described in sub-elements of PlanDefinition.action, at least for the same-group activities.

  • When defined between activities within the same activity group, the PlanDefinition.action.relatedAction.offset (typically in the variant offsetDuration) defines a pause between the activities often specified in minutes or seconds.

  • When defined between activities no in the same activity group, the same offset defines different measurement regimes, for instance that a one activity starts a month after another ends. The offset is often specified in months or days.

Note

It is expected that a Telemedicine Solution treats offset between activities in the same activity group as a pause for which countdown or count up should be presented to the user (typically the individual following the plan). In case it is not specified whether to perform countdown or count up (this is currently not modelled), the Telemedicine Solution shall perform countdown.

An activity may be described with a duration for actually performing the activity, beside a measurement regime. When this is the case, the:

  • PlanDefinition.action.timing[x] describes its measurement regime, while

  • ActivityDefinition.timingRange or, typically, ActivityDefinition.timingDuration describes the duration of actually performing the activity

Note

It is expected that a Telemedicine Solution treats activity duration as situation where countdown or count up should be presented to the user (typically the individual following the plan). In case it is not specified whether to perform countdown or count up (this is currently not modelled), the Telemedicine Solution shall perform countdown.

Ensuring Use of Proper Units

...

Note

It is expected that a Solution or Telemedicine Solution component ensures that measurement data conforms to the expected measurement unit. Correctness (and verification hereof) of any required conversion in that regard is the responsibility of the Solution or Telemedicine Solution component.

Preparing Measurements for Submission

...

Note

It is expected that a Telemedicine Solution detects the use of participant.type set to device and prepares submission of a measurement based on a value extracted from sibling activities rather than involving the Patient. Typically, this scenario involves the Telemedicine Solution preparing an Observation with value based on or extracted from a QuestionnaireResponse.

...

Note

It is expected that a Telemedicine Solution (typically a Citizen Solution) places multiple measurements into partitions each with measurements sharing same or similar resolve timing, and, furthermore, submits each partition as an individual invocation of $submit-measurement.