Intersection of http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-devicerequest and http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-devicerequest

This is the set of resources that conform to both CRD Device Request (http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-devicerequest) and CRD Device Request (http://hl7.org/fhir/us/davinci-crd/StructureDefinition/profile-devicerequest).

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. DeviceRequest 0..*Medical device request
... 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..*ExtensionExtension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣ0..*IdentifierExternal Request identifier
... instantiatesCanonical Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn SΣ0..*Reference(Resource)What request fulfills
... priorRequest Σ0..*Reference(Resource)What request replaces
... groupIdentifier Σ0..1IdentifierIdentifier of composite request
... status ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
Binding: ?? (required): Codes representing the status of the request.
Example General: draft
... intent ?!Σ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
Binding: ?? (required): The kind of diagnostic request.
... priority Σ0..1coderoutine | urgent | asap | stat
Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.
... code[x] SΣ1..1Device requested
Binding: ?? (extensible)
.... codeReferenceReference(CRD Device | #sd-profile-device-profile-device)
.... codeCodeableConceptCodeableConcept
... parameter S0..*BackboneElementDevice details
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... code 0..1CodeableConceptDevice detail
Binding Description: (example): A code that identifies the device detail.
.... value[x] 0..1Value of detail
..... valueCodeableConceptCodeableConcept
..... valueQuantityQuantity
..... valueRangeRange
..... valueBooleanboolean
... subject SΣ1..1Reference(CRD Patient | #sd-profile-patient-profile-patient)Focus of request
... encounter Σ0..1Reference(CRD Encounter | #sd-profile-encounter-profile-encounter)Encounter motivating request
... occurrence[x] SΣ0..1Desired time or schedule for use
.... occurrenceDateTimedateTime
.... occurrencePeriodPeriod
.... occurrenceTimingTiming
... authoredOn SΣ1..1dateTimeWhen recorded
... requester SΣ1..1Reference(US Core Practitioner Profile(7.0.0) S | HRex PractitionerRole Profile S)Who/what is requesting diagnostics
... performerType Σ0..1CodeableConceptFiller role
Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.
... performer SΣ0..1Reference(US Core Practitioner Profile(7.0.0) S | HRex PractitionerRole Profile S)Requested Filler
... reasonCode SΣ0..*CodeableConceptCoded Reason for request
Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the device.
... reasonReference SΣ0..*Reference(US Core Condition Problems and Health Concerns Profile(7.0.0) | US Core Condition Encounter Diagnosis Profile(7.0.0) | US Core DiagnosticReport Profile for Laboratory Results Reporting(7.0.0) | US Core DiagnosticReport Profile for Report and Note Exchange(7.0.0) | US Core DocumentReference Profile(7.0.0) | Observation)Linked Reason for request
... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... supportingInfo 0..*Reference(Resource)Additional clinical information
... note 0..*AnnotationNotes or comments
... relevantHistory 0..*Reference(Provenance)Request provenance

doco Documentation for this format