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

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

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. ServiceRequest C0..*A request for a service to be performed
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
... 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..*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..1codeleft: proposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option; right: Note: To allow for the resource life cycle, no constraint on intent, use "directive" in PMO document
Binding: ?? (required): The kind of service request.
... category SΣ0..*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 ?!Σ0..1booleanTrue if service/procedure should not be performed
... code SΣ1..1CodeableConceptWhat is being requested/ordered
Binding Description: (extensible) ⚠: Portable Medical Order panel answers - mostly free-text
.... extension 0..*ExtensionAdditional content defined by implementations
.... coding Σ0..*CodingCode defined by a terminology system
.... text SΣ0..1stringleft: 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: The name of the test, procedure, or service to be performed.; right: Plain text representation of the PMO procedure or service.
... orderDetail SΣ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 S | Group | US Core Location Profile | Device)left: Individual or Entity the service is ordered for; right: limited to Patient
... encounter SΣ0..1Reference(US Core Encounter Profile)left: Encounter in which the request was created; right: **NOT USED WHEN PART OF A PMO DOCUMENT**
... occurrence[x] SΣ0..1left: When service should occur; right: Often just a start date
.... 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..1dateTimeleft: Date request signed; right: Date Order signed vs date of PMO document - same if part of PMO document
... requester SΣ0..1Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core RelatedPerson Profile | Device)left: Who/what is requesting service; right: Authored only by Practitioner
... 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 SΣ0..*CodeableConceptleft: 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Explanation/Justification for procedure or service; right: Explanation/Justification for procedure or service
Binding: ?? (extensible)
... reasonReference SΣ0..*left: 𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile that supports the requested service; right: US Core ADI DocumentReference Profile or other US Core profiles that support the requested PMO service.
... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... supportingInfo 0..*Reference(Resource)Additional clinical information
... specimen Σ0..*Reference(Specimen)Procedure Samples
... bodySite Σ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