Generated Narrative: StructureDefinition EHDSServiceRequestLaboratoryObligations Language: en Name Flags Card. Type Description & Constraints EHDSServiceRequest 0..* EHDSServiceRequest Service request model #xD; header #xD; subject O 1..1 EHDSPatient Patient/subject information Obligations Actor SHALL:able-to-populate Producer #xD; identifier O 0..* Identifier Business identifier for the object, unique within its system. Supporting disambiguation between different contexts (systems/countries). Obligations Actor SHOULD:able-to-populate Producer #xD; author[x] O 0..* EHDSHealthProfessional, EHDSOrganisation, EHDSDevice Author(s) responsible for the provided information. Obligations Actor SHALL:able-to-populate Producer #xD; date O 0..1 dateTime Date and optionally time of authoring/issuing Obligations Actor SHALL:able-to-populate Producer #xD; status O 1..1 CodeableConcept Status of the resource or document Obligations Actor SHALL:able-to-populate Producer #xD; description O 0..1 string Textual description of the requested service Obligations Actor SHOULD:able-to-populate Producer SHALL:display Consumer #xD; code O 0..1 CodeableConcept A code and name that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. Obligations Actor SHALL:able-to-populate Producer SHALL:display Consumer #xD; quantity O 0..1 Quantity Amount of requested services of the same type Obligations Actor SHALL:able-to-populate Producer #xD; reason[x] O 0..* EHDSObservation, EHDSCondition, EHDSMedication, string Reason why this service is being requested. Obligations Actor SHOULD:able-to-populate Producer #xD; priority O 0..1 CodeableConcept Indicates how quickly the request should be addressed with respect to other requests. Obligations Actor SHOULD:able-to-populate Producer #xD; supportingInformation[x] O 0..* EHDSObservation, EHDSCondition, EHDSProcedure, EHDSMedicationAdministration Health conditions relevant for the results interpretation, e.g. fasting status, sex for clinical use, etc. Obligations Actor SHOULD:able-to-populate Producer #xD; specimen O 0..* EHDSSpecimen Specimens to be used by the laboratory procedure Obligations Actor SHALL:able-to-populate Producer #xD; Documentation for this format
Service request laboratory specific obligations
Obligations for the logical model of service request in the scope of laboratory use case
The model covers details about a requested service or services. One order may include several requests.
EHR systems SHALL provide information about the subject of care (patient).
A business identifier SHALL be populated, if known.
Business identifier for the object, unique within its system. Supporting disambiguation between different contexts (systems/countries).
Service request authorship SHALL be present.
Author(s) responsible for the provided information.
Author(s) responsible for the provided information. The exact role of the responsible author varies across use cases and is specific to individual models.
Date and optionally time of authoring/issuing
SHALL be able to populate status of the service request.
Source of information (e.g. patient, patient's proxy). Used in case the patient has authored the information or the author has submitted patient-stated information.
Language in which the resource is written. Language is expressed by the IETF language tag.
SHALL populate service request note, if known.
Textual description of the requested service
SHALL populate type of requested service
A code and name that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested.
Quantity of requested service SHALL be populated
Amount of requested services of the same type
Anatomic location and laterality where the procedure should be performed. This is the target site.
Reason for service request SHALL be populated
Reason why this service is being requested.
SHALL be able to populate service request priority, if known.
Indicates how quickly the request should be addressed with respect to other requests.
SHALL populate supporting information for the servce request, e.g. Medication, Procedure, Observation, etc., if known.
Health conditions relevant for the results interpretation, e.g. fasting status, sex for clinical use, etc.
SHALL populate related specimen, if known.
Specimens to be used by the laboratory procedure
The encounter that provides additional information about the healthcare context in which this request is made.
Patient or consumer-oriented instructions