Release 4B Snapshot #1
WorkflowThis page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R5 R4B R4
| Orders and Observations Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Device, Encounter, Patient, Practitioner |
This is a representation of the json schema for DeviceRequest, which is just a part of the full JSON Schema.
{
"$schema": "http://json-schema.org/draft-06/schema#",
"id": "http://hl7.org/fhir/json-schema/DeviceRequest",
"$ref": "#/definitions/DeviceRequest",
"description": "see http://hl7.org/fhir/json.html#schema for information about the FHIR Json Schemas",
"definitions": {
"DeviceRequest": {
"description": "Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.",
"properties": {
"resourceType": {
"description": "This is a DeviceRequest resource",
"const": "DeviceRequest"
},
"id": {
"description": "The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.",
"$ref": "string.schema.json#/definitions/string"
},
"meta": {
"description": "The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.",
"$ref": "Meta.schema.json#/definitions/Meta"
},
"implicitRules": {
"description": "A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.",
"$ref": "#/definitions/uri"
},
"_implicitRules": {
"description": "Extensions for implicitRules",
"$ref": "Element.schema.json#/definitions/Element"
},
"language": {
"description": "The base language in which the resource is written.",
"$ref": "#/definitions/code"
},
"_language": {
"description": "Extensions for language",
"$ref": "Element.schema.json#/definitions/Element"
},
"text": {
"description": "A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it \"clinically safe\" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.",
"$ref": "Narrative.schema.json#/definitions/Narrative"
},
"contained": {
"description": "These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.",
"items": {
"$ref": "ResourceList.schema.json#/definitions/ResourceList"
},
"type": "array"
},
"extension": {
"description": "May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"modifierExtension": {
"description": "May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element\u0027s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"identifier": {
"description": "Identifiers assigned to this order by the orderer or by the receiver.",
"items": {
"$ref": "Identifier.schema.json#/definitions/Identifier"
},
"type": "array"
},
"instantiatesCanonical": {
"description": "The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest.",
"items": {
"$ref": "canonical.schema.json#/definitions/canonical"
},
"type": "array"
},
"instantiatesUri": {
"description": "The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this DeviceRequest.",
"items": {
"$ref": "#/definitions/uri"
},
"type": "array"
},
"_instantiatesUri": {
"description": "Extensions for instantiatesUri",
"items": {
"$ref": "Element.schema.json#/definitions/Element"
},
"type": "array"
},
"basedOn": {
"description": "Plan/proposal/order fulfilled by this request.",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"priorRequest": {
"description": "The request takes the place of the referenced completed or terminated request(s).",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"groupIdentifier": {
"description": "Composite request this is part of.",
"$ref": "Identifier.schema.json#/definitions/Identifier"
},
"status": {
"description": "The status of the request.",
"$ref": "#/definitions/code"
},
"_status": {
"description": "Extensions for status",
"$ref": "Element.schema.json#/definitions/Element"
},
"intent": {
"description": "Whether the request is a proposal, plan, an original order or a reflex order.",
"$ref": "#/definitions/code"
},
"_intent": {
"description": "Extensions for intent",
"$ref": "Element.schema.json#/definitions/Element"
},
"priority": {
"description": "Indicates how quickly the {{title}} should be addressed with respect to other requests.",
"$ref": "#/definitions/code"
},
"_priority": {
"description": "Extensions for priority",
"$ref": "Element.schema.json#/definitions/Element"
},
"codeReference": {
"description": "The details of the device to be used.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"codeCodeableConcept": {
"description": "The details of the device to be used.",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"parameter": {
"description": "Specific parameters for the ordered item. For example, the prism value for lenses.",
"items": {
"$ref": "#/definitions/DeviceRequest_Parameter"
},
"type": "array"
},
"subject": {
"description": "The patient who will use the device.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"encounter": {
"description": "An encounter that provides additional context in which this request is made.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"occurrenceDateTime": {
"description": "The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. \"Every 8 hours\"; \"Three times a day\"; \"1/2 an hour before breakfast for 10 days from 23-Dec 2011:\"; \"15 Oct 2013, 17 Oct 2013 and 1 Nov 2013\".",
"pattern": "^([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(-(0[1-9]|1[0-2])(-(0[1-9]|[1-2][0-9]|3[0-1])(T([01][0-9]|2[0-3]):[0-5][0-9]:([0-5][0-9]|60)(\\.[0-9]+)?(Z|(\\+|-)((0[0-9]|1[0-3]):[0-5][0-9]|14:00)))?)?)?$",
"type": "string"
},
"_occurrenceDateTime": {
"description": "Extensions for occurrenceDateTime",
"$ref": "Element.schema.json#/definitions/Element"
},
"occurrencePeriod": {
"description": "The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. \"Every 8 hours\"; \"Three times a day\"; \"1/2 an hour before breakfast for 10 days from 23-Dec 2011:\"; \"15 Oct 2013, 17 Oct 2013 and 1 Nov 2013\".",
"$ref": "Period.schema.json#/definitions/Period"
},
"occurrenceTiming": {
"description": "The timing schedule for the use of the device. The Schedule data type allows many different expressions, for example. \"Every 8 hours\"; \"Three times a day\"; \"1/2 an hour before breakfast for 10 days from 23-Dec 2011:\"; \"15 Oct 2013, 17 Oct 2013 and 1 Nov 2013\".",
"$ref": "Timing.schema.json#/definitions/Timing"
},
"authoredOn": {
"description": "When the request transitioned to being actionable.",
"$ref": "#/definitions/dateTime"
},
"_authoredOn": {
"description": "Extensions for authoredOn",
"$ref": "Element.schema.json#/definitions/Element"
},
"requester": {
"description": "The individual who initiated the request and has responsibility for its activation.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"performerType": {
"description": "Desired type of performer for doing the diagnostic testing.",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"performer": {
"description": "The desired performer for doing the diagnostic testing.",
"$ref": "Reference.schema.json#/definitions/Reference"
},
"reasonCode": {
"description": "Reason or justification for the use of this device.",
"items": {
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"type": "array"
},
"reasonReference": {
"description": "Reason or justification for the use of this device.",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"insurance": {
"description": "Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"supportingInfo": {
"description": "Additional clinical information about the patient that may influence the request fulfilment. For example, this may include where on the subject\u0027s body the device will be used (i.e. the target site).",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
},
"note": {
"description": "Details about this request that were not represented at all or sufficiently in one of the attributes provided in a class. These may include for example a comment, an instruction, or a note associated with the statement.",
"items": {
"$ref": "Annotation.schema.json#/definitions/Annotation"
},
"type": "array"
},
"relevantHistory": {
"description": "Key events in the history of the request.",
"items": {
"$ref": "Reference.schema.json#/definitions/Reference"
},
"type": "array"
}
},
"additionalProperties": false,
"required": [
"subject",
"resourceType"
]
},
"DeviceRequest_Parameter": {
"description": "Represents a request for a patient to employ a medical device. The device may be an implantable device, or an external assistive device, such as a walker.",
"properties": {
"id": {
"description": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
"$ref": "string.schema.json#/definitions/string"
},
"extension": {
"description": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"modifierExtension": {
"description": "May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element\u0027s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"items": {
"$ref": "Extension.schema.json#/definitions/Extension"
},
"type": "array"
},
"code": {
"description": "A code or string that identifies the device detail being asserted.",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"valueCodeableConcept": {
"description": "The value of the device detail.",
"$ref": "CodeableConcept.schema.json#/definitions/CodeableConcept"
},
"valueQuantity": {
"description": "The value of the device detail.",
"$ref": "Quantity.schema.json#/definitions/Quantity"
},
"valueRange": {
"description": "The value of the device detail.",
"$ref": "Range.schema.json#/definitions/Range"
},
"valueBoolean": {
"description": "The value of the device detail.",
"pattern": "^true|false$",
"type": "boolean"
},
"_valueBoolean": {
"description": "Extensions for valueBoolean",
"$ref": "Element.schema.json#/definitions/Element"
}
},
"additionalProperties": false
}
}
}
FHIR ®© HL7.org 2011+. FHIR R4B Ballot #1 hl7.fhir.core#4.3.0-snapshot1 generated on Mon, Dec 20, 2021 14:14+1100.
Links: Search |
Version History |
Table of Contents |
QA Page |
Compare to R4 |
|
Propose a change