## Intersection of http://hl7.org/fhir/us/core/StructureDefinition/us-core-pmo-servicerequest and http://hl7.org/fhir/us/dapl/StructureDefinition/dapl-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 DAPL ServiceRequest (http://hl7.org/fhir/us/dapl/StructureDefinition/dapl-servicerequest).

### Structure

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
ServiceRequest | C | 0..* |  | left: A request for a service to be performed; right: DAPL ServiceRequest Constraints: prr-1
meta | Σ | 0..1 | Meta | Metadata about the resource
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created
language |  | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
extension |  | 0..* | Extension | Additional content defined by implementations
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
identifier | Σ | 0..* | Identifier | Identifiers assigned to this order
instantiatesCanonical | Σ | 0..* | canonical(ActivityDefinition | PlanDefinition) | Instantiates FHIR protocol or definition
instantiatesUri | Σ | 0..* | uri | Instantiates external protocol or definition
basedOn | Σ | 0..* | Reference(CarePlan | ServiceRequest | MedicationRequest) | What request fulfills
replaces | Σ | 0..* | Reference(ServiceRequest) | What request replaces
requisition | Σ | 0..1 | Identifier | Composite Request ID
status | ?!S Σ | 1..1 | code | draft | active | on-hold | revoked | completed | entered-in-error | unknown Binding: ?? (required): The status of a service order.
intent | ?!S Σ | 1..1 | code | proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): The kind of service request.
category | S Σ | 1..* | CodeableConcept | Classification of service Binding: ?? (example): Classification of the requested service.
priority | Σ | 0..1 | code | routine | urgent | asap | stat Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.
doNotPerform | ?!S Σ | 1..1 | boolean | True if service/procedure should not be performed
code | S Σ | 1..1 | CodeableConcept | What is being requested/ordered Binding: ?? (extensible): The set of codes indicating the ServiceRequests
orderDetail | Σ | 0..* | CodeableConcept | Additional order information Binding: ?? (example): Codified order entry details which are based on order context.
quantity[x] | Σ | 0..1 |  | Service amount
quantityQuantity |  |  | Quantity |
quantityRatio |  |  | Ratio |
quantityRange |  |  | Range |
subject | S Σ | 1..1 | Reference(US Core Patient Profile | #sd+4-us-core-patient-dapl-deidentified-patient) | Individual or Entity the service is ordered for
encounter | S Σ | 0..1 | Reference(US Core Encounter Profile | #sd+20-us-core-encounter-dapl-deidentified-encounter) | Encounter in which the request was created
occurrence[x] | S Σ | 0..1 |  | When service should occur
occurrencePeriod |  |  | Period S |
occurrenceDateTime |  |  | dateTime |
occurrenceTiming |  |  | Timing |
asNeeded[x] | Σ | 0..1 |  | Preconditions 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.
asNeededBoolean |  |  | boolean |
asNeededCodeableConcept |  |  | CodeableConcept |
authoredOn | S Σ | 0..1 | dateTime | Date request signed
requester | S Σ | 0..1 | Reference(US Core Practitioner Profile S | US Core Organization Profile | PractitionerRole) | Who/what is requesting service
performerType | Σ | 0..1 | CodeableConcept | Performer 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..* | CodeableConcept | Requested location Binding: ?? (example): A location type where services are delivered.
locationReference | Σ | 0..* | Reference(Location) | Requested location
reasonCode | Σ | 0..* | CodeableConcept | Explanation/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..* | CodeableConcept | Location on Body Binding: ?? (example): Codes describing anatomical locations. May include laterality.
note |  | 0..* | Annotation | Comments
patientInstruction | Σ | 0..1 | string | Patient or consumer-oriented instructions
relevantHistory |  | 0..* | Reference(Provenance) | Request provenance
Documentation for this format