Intersection of http://hl7.org/fhir/us/core/StructureDefinition/us-core-pmo-servicerequest and http://hl7.org/fhir/us/uds-plus/StructureDefinition/uds-plus-servicerequest

This is the set of resources that conform to both US Core PMO ServiceRequest Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-pmo-servicerequest) and De-Identified UDS Plus ServiceRequest (http://hl7.org/fhir/us/uds-plus/StructureDefinition/uds-plus-servicerequest).

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. ServiceRequest C0..*left: A request for a service to be performed; right: De-Identified UDS Plus ServiceRequest
Constraints: 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: ?? (preferred): A human language.
Additional BindingsPurpose
??Max Binding
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierIdentifiers assigned to this 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 Σ0..1IdentifierComposite Request ID
... status ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
Binding: ?? (required): The status of a service order.
... intent ?!SΣ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Binding: ?? (required): The kind of service request.
... category SΣ1..*CodeableConceptClassification of service
Binding: ?? (example): Classification of the requested service.
... priority Σ0..1coderoutine | urgent | asap | stat
Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.
... doNotPerform ?!SΣ1..1booleanTrue if service/procedure should not be performed
... code SΣ1..1CodeableConceptWhat is being requested/ordered
Binding: ?? (extensible): The set of codes indicating the ServiceRequests
... orderDetail Σ0..*CodeableConceptAdditional order information
Binding: ?? (example): Codified order entry details which are based on order context.
... quantity[x] Σ0..1Service amount
.... quantityQuantityQuantity
.... quantityRatioRatio
.... quantityRangeRange
... subject SΣ1..1Reference(US Core Patient Profile | #sd-us-core-patient-de-identified-uds-plus-patient)Individual or Entity the service is ordered for
... encounter SΣ0..1Reference(US Core Encounter Profile | #sd-us-core-encounter-uds-plus-encounter)Encounter in which the request was created
... occurrence[x] SΣ0..1When service should occur
.... occurrencePeriodPeriod S
.... occurrenceDateTimedateTime
.... 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..1dateTimeDate request signed
... requester SΣ0..1Reference(US Core Practitioner Profile S | US Core Organization Profile | PractitionerRole)Who/what is requesting service
... 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
... locationCode Σ0..*CodeableConceptRequested location
Binding: ?? (example): A location type where services are delivered.
... locationReference Σ0..*Reference(Location)Requested location
... reasonCode Σ0..*CodeableConceptExplanation/Justification for procedure or service
Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.
... reasonReference SΣ0..*left: Reference to the PMO document; right: Explanation/Justification for service or service
... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... supportingInfo 0..*Reference(Resource)Additional clinical information
... specimen Σ0..*Reference(Specimen)Procedure Samples
... bodySite SΣ0..*CodeableConceptLocation on Body
Binding: ?? (example): Codes describing anatomical locations. May include laterality.
... note 0..*AnnotationComments
... patientInstruction Σ0..1stringPatient or consumer-oriented instructions
... relevantHistory 0..*Reference(Provenance)Request provenance

doco Documentation for this format