Intersection of http://fhir.ch/ig/ch-elm/StructureDefinition/ch-elm-servicerequest-laboratory-order and http://fhir.ch/ig/ch-elm/StructureDefinition/ch-elm-servicerequest-laboratory-order

This is the set of resources that conform to both CH ELM ServiceRequest: Laboratory Order (http://fhir.ch/ig/ch-elm/StructureDefinition/ch-elm-servicerequest-laboratory-order) and CH ELM ServiceRequest: Laboratory Order (http://fhir.ch/ig/ch-elm/StructureDefinition/ch-elm-servicerequest-laboratory-order).

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. ServiceRequest C0..*CH ELM ServiceRequest: Laboratory Order
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 Σ1..1IdentifierIdentifiers assigned to this order
.... extension 0..*ExtensionAdditional content defined by implementations
.... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
Binding: ?? (required): Identifies the purpose for this identifier, if known .
.... type Σ0..1CodeableConceptDescription of identifier
Binding: ?? (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
.... system Σ0..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
.... value Σ1..1stringThe value that is unique
Example General: 123456
Max Length:100
.... period Σ0..1PeriodTime period when id is/was valid for use
.... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
... instantiatesCanonical Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*What request fulfills
... replaces Σ0..*Reference(ServiceRequest)What request replaces
... requisition SΣ0..1Identifierleft: Original order identifier; right: Original order identifier, use basedOn ServiceRequest identifier if additional order information is provided
... status ?!Σ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
Binding: ?? (required): The status of a service order.
... intent ?!Σ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Binding: ?? (required): The kind of service request.
... category Σ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 Σ1..1??, ??What is being requested/ordered
Binding: ?? (preferred)
... 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 Σ1..1Individual or Entity the service is ordered for
... encounter Σ0..1Reference(Encounter)Encounter in which the request was created
... occurrence[x] Σ0..1When service should occur
.... 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 Σ0..1dateTimeWhen the order was placed
... requester Σ1..1Reference(CH ELM PractitionerRole: Orderer | #sd-ch-elm-practitionerrole-orderer-ch-elm-practitionerrole-orderer)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 Σ0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)Explanation/Justification for service or service
... insurance 0..*Reference(Coverage)Associated insurance coverage
... supportingInfo 0..*Reference(Resource)Additional information: e.g AOEs and prior results
... specimen Σ1..1Reference(CH ELM Specimen: Laboratory | #sd-ch-elm-specimen-ch-elm-specimen)Specimens to be used by the laboratory procedure
... 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