Patient-specific clinical order for a digital (eHealth) activity that a healthcare professional requests for a patient, such as completing a questionnaire, performing home measurements, viewing educational content, or launching a third-party module.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Business identifier that uniquely identifies this ServiceRequest within or across systems.

Current state of the service request (e.g. draft, active, completed, cancelled).

Indicates the level of authority or intention associated with the request (e.g., order or plan).

Patient for whom the digital activity is requested.

Patient or consumer-oriented instructions for how the requested activity should be performed. Use this element for patient-specific guidance that should be shown alongside the Task(s) executing this order (e.g., home blood pressure monitoring for 8 weeks, once daily in the morning).

Requested schedule for performing the provider module, such as duration, frequency and time of day.

Healthcare professional role that requests this activity for the patient.

Date and time when this service request was created.

Patient-specific clinical order for a digital (eHealth) activity that a healthcare professional requests for a patient, such as completing a questionnaire, performing home measurements, viewing educational content, or launching a third-party module.

Business identifier that uniquely identifies this ServiceRequest within or across systems.

Current state of the service request (e.g. draft, active, completed, cancelled).

Indicates the level of authority or intention associated with the request (e.g., order or plan).

Patient for whom the digital activity is requested.

Patient or consumer-oriented instructions for how the requested activity should be performed. Use this element for patient-specific guidance that should be shown alongside the Task(s) executing this order (e.g., home blood pressure monitoring for 8 weeks, once daily in the morning).

Requested schedule for performing the provider module, such as duration, frequency and time of day.

Healthcare professional role that requests this activity for the patient.

Date and time when this service request was created.

Patient-specific clinical order for a digital (eHealth) activity that a healthcare professional requests for a patient, such as completing a questionnaire, performing home measurements, viewing educational content, or launching a third-party module.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Business identifier that uniquely identifies this ServiceRequest within or across systems.

Current state of the service request (e.g. draft, active, completed, cancelled).

Indicates the level of authority or intention associated with the request (e.g., order or plan).

Patient for whom the digital activity is requested.

Patient or consumer-oriented instructions for how the requested activity should be performed. Use this element for patient-specific guidance that should be shown alongside the Task(s) executing this order (e.g., home blood pressure monitoring for 8 weeks, once daily in the morning).

Requested schedule for performing the provider module, such as duration, frequency and time of day.

Healthcare professional role that requests this activity for the patient.

Date and time when this service request was created.