Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

THIS SECTION IS STILL UNDER CONSTRUCTION.

Preparing for Submitting

Determining Resolved Timing to Use

The functionality described below is provided with eHealth Infrastructure Release 7 and after.

When submitting measurements, it is mandatory to specify resolved timing (see https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/1661665301/Adhering+to+Care+Plans+and+Measurement+Regimes#When-an-Activity-is-Supposed-to-Happen---The-Notion-of-Resolved-Timing ) information in the ehealth-resolved-timing element of Observation, QuestionnaireResponse and Media. The structure of ehealth-resolved-timing contains:

  • serviceRequestVersionId which must specify the current FHIR technical version of the ServiceRequestreferenced in basedOn element of Observation, QuestionnaireResponse and Media.

  • start - start datetime of resolved timing period. This is mandatory when type is Resolved.

  • end - end datetime of resolved timing period. This is mandatory when type is Resolved.

  • type

    • Resolved if the ServiceRequest has a measurement regime supported by the infrastructure

    • Unresolved if the ServiceRequest has a measurement regime not supported by the infrastructure

    • Adhoc if the ServiceRequest has a measurement regime is specified as ad-hoc or the measurement was collected as per request from a practitioner.

One way to determine what resolved time to used is to invoke the get-patient-procedures operation.

Determining Qualities

The described approach is still under refinement. Neither the required Questionnaire nor Library is available in the eHealth Infrastructure at the time of writing.

Saving a Draft QuestionnaireResponse

A draft QuestionnaireResponse can be saved by creating a new QuestionnaireResponse with status in-progress and subsequently updating it. This is performed through QuestionnaireResponse Create and Update, respectively, which is enabled for status in-progress only. Whether it is used for autosave or manually initiated, the client should refrain from calling QuestionnaireResponse Update unless actual changes have been made to the QuestionnaireResponse. Calling QuestionnaireResponse Update without actual change leads to unneccesary load and will not result in change of the QuestionnaireResponse in the database anyway.

When creating/updating a draft QuestionnaireResponse, make sure the following elements are set:

  • status is in-progress

  • basedOn references the ServiceRequest stating that answering of questionnaire should be performed as activity

  • resolvedTiming reflects the resolved timing with which the QuestionnaireResponse intended to be submitted (as final).

Cleanup of draft QuestionnaireResponse

When the final version of the QuestionnaireResponse is submitted with $submit-measurement, any corresponding draft QuestionnaireResponse is automatically deleted. The criteria involved in finding corresponding draft(s) are QuestionnaireResponse with:

  • status set to in-progress

  • basedOn is same as that of submitted QuestionnaireResponse

  • resolvedTiming is same as that of submitted QuestionnaireResponse

There is no guarantee that a draft QuestionnaireResponse is ever submitted. Therefore, a periodic and automatic Infrastructure job performs deletion of QuestionnaireResponse with:

  • status is in-progress

  • lastUpdated is older than a configurable retention period, currently set to 30 days.

Preparing an Observation for Score Calculated from a QuestionnaireResponse

Preparing an Observation for Body Mass Index

Submitting

TBD

  • No labels