Union of https://dhp.uz/fhir/core/StructureDefinition/uz-core-servicerequest and https://dhp.uz/fhir/core/StructureDefinition/uz-core-servicerequest

This is the set of resources that conform to either of the profiles UZ Core ServiceRequest (https://dhp.uz/fhir/core/StructureDefinition/uz-core-servicerequest) and UZ Core ServiceRequest (https://dhp.uz/fhir/core/StructureDefinition/uz-core-servicerequest). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. ServiceRequest C0..*A request for a service to be performed
Constraints: bdystr-1, prr-1
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: ?? (required): IETF language tag for a human language
... text 0..1NarrativeText summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionExtension
Constraints: ext-1
... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
Constraints: ext-1
... identifier SΣ0..*IdentifierUnique identifier for the (e.g., laboratory) referral or order.
... instantiatesCanonical Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(CarePlan | ServiceRequest | MedicationRequest)What request fulfills
... replaces Σ0..*Reference(ServiceRequest)What request replaces
... requisition SΣ0..1IdentifierA common identifier used to group multiple ServiceRequest resources created as part of a single referral, visit, or a single specimen collection episode.
... status ?!SΣ1..1codeThe status of a service order
Binding: ?? (required)
... intent ?!SΣ1..1codeIndicates the level of obligation and intent of the service request, specifying whether the request represents an official order to be performed.
Binding: ?? (required)
... category SΣ0..*CodeableConceptThe category of the service being requested, such as laboratory, imaging, or procedural care. This element provides a high-level classification of the type of service being ordered.
Binding: ?? (extensible)
... priority SΣ0..1codeIndicates how quickly the ServiceRequest should be addressed with respect to other requests
Binding: ?? (required)
... doNotPerform ?!SΣ0..1booleanIndicates that the service described by the ServiceRequest should not be performed.
... code SΣ0..1CodeableReference(ActivityDefinition | PlanDefinition)Specifies the procedure, diagnostic investigation, or panel being requested. The codes used represent orderable services and must not be used for analytical result observations.
Binding: ?? (extensible)
... orderDetail Σ0..*BackboneElementAdditional order information
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... parameterFocus 0..1CodeableReference(Device | DeviceDefinition | DeviceRequest | SupplyRequest | Medication | MedicationRequest | BiologicallyDerivedProduct | Substance)The context of the order details by reference
.... parameter Σ1..*BackboneElementThe parameter details for the service being requested
..... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
..... code Σ1..1CodeableConceptThe detail of the order being requested
Binding: ?? (example): Codes for order detail parameters.
..... value[x] Σ1..1The value for the order detail
...... valueQuantityQuantity
...... valueRatioRatio
...... valueRangeRange
...... valueBooleanboolean
...... valueCodeableConceptCodeableConcept
...... valueStringstring
...... valuePeriodPeriod
... quantity[x] Σ0..1Service amount
.... quantityQuantityQuantity
.... quantityRatioRatio
.... quantityRangeRange
... subject SΣ1..1Reference(UZ Core Patient(0.9.0) | UZ Core Location(0.9.0) | #sd-808-uz-core-patient-uz-core-patient)The patient for whom the laboratory referral or order is issued. This element identifies the individual who is the subject of the requested laboratory investigation.
... focus Σ0..*Reference(Resource)What the service request is about, when it is not about the subject of record
... encounter SΣ0..1Reference(UZ Core Encounter(0.9.0) | #sd-828-uz-core-encounter-uz-core-encounter)The healthcare encounter during which the laboratory referral or order was created or to which the laboratory investigation is related. This element provides clinical context for the ServiceRequest, such as an outpatient visit or inpatient hospitalization.
... occurrence[x] SΣ0..1This element is used to indicate the intended or actual timing of the laboratory service
.... occurrenceDateTimedateTime
.... occurrencePeriodPeriod
.... occurrenceTimingTiming
... asNeeded[x] Σ0..1Preconditions for service
Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.
.... asNeededBooleanboolean
.... asNeededCodeableConceptCodeableConcept
... authoredOn SΣ0..1dateTimeThe date and time when the ServiceRequest was authored and formally issued by the requester.
... requester SΣ0..1Reference(UZ Core Practitioner(0.9.0) | UZ Core PractitionerRole(0.9.0) | UZ Core Organization(0.9.0) | UZ Core Patient(0.9.0) | UZ Core RelatedPerson(0.9.0) | #sd-789-uz-core-practitioner-uz-core-practitioner)The individual, role, or organization that authored and issued the laboratory referral/order. This element identifies the healthcare professional or organizational unit responsible for initiating the ServiceRequest.
... performerType Σ0..1CodeableConceptPerformer role
Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)Requested performer
... location Σ0..*CodeableReference(Location)Requested location
Binding: ?? (example): A location type where services are delivered.
... reason SΣ0..*CodeableReference(Condition | Observation | DiagnosticReport | DocumentReference | DetectedIssue)A reason to a Condition or other clinical resource that represents the medical justification for the laboratory referral, such as a diagnosis coded using ICD-10. This allows structured representation of diagnosis details including onset date and clinical status.
Binding: ?? (required)
... insurance S0..*Reference(Coverage)Insurance coverage or funding source applicable to the requested service.
... supportingInfo S0..*CodeableReference(ServiceRequest)Additional clinical or administrative information supporting or justifying the requested service.
... specimen SΣ0..*Reference(UZ Core Specimen(0.9.0) | #sd-868-uz-core-specimen-uz-core-specimen)The specimen or specimens to be analyzed as part of the requested laboratory service.
... bodySite Σ0..*CodeableConceptCoded location on Body
Binding: ?? (example): SNOMED CT Body site concepts
... bodyStructure Σ0..1Reference(BodyStructure)BodyStructure-based location on the body
... note 0..*AnnotationDoctor's comment or conclution upon referral
... patientInstruction S0..*BackboneElementInstructions in terms that are understood by the patient or their caregiver regarding the laboratory service, such as preparation requirements or post-service care instructions.
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... instruction[x] Σ0..1Patient or consumer-oriented instructions
..... instructionMarkdownmarkdown
..... instructionReferenceReference(DocumentReference)
... relevantHistory 0..*Reference(Provenance)Request provenance

doco Documentation for this format