{
"description": null,
"_filename": "DwServiceRequest.StructureDefinition.json",
"package_name": "telus.dw.emr.extract",
"date": "2024-05-03T22:11:40.4165223+00:00",
"derivation": "constraint",
"publisher": null,
"fhirVersion": "4.0.1",
"name": "DwServiceRequest",
"abstract": false,
"type": "ServiceRequest",
"experimental": null,
"resourceType": "StructureDefinition",
"title": null,
"package_version": "1.0.0",
"status": "draft",
"id": "f5f8392d-9406-4462-8ad2-184f16e57285",
"kind": "resource",
"url": "https://www.telus.com/health/fhir/dwemrextract/StructureDefinition/DwServiceRequest",
"version": null,
"differential": {
"element": [ {
"id": "ServiceRequest.id",
"min": 1,
"path": "ServiceRequest.id",
"mustSupport": true
}, {
"id": "ServiceRequest.meta",
"path": "ServiceRequest.meta",
"mustSupport": false
}, {
"id": "ServiceRequest.meta.lastUpdated",
"min": 1,
"path": "ServiceRequest.meta.lastUpdated"
}, {
"id": "ServiceRequest.meta.source",
"min": 1,
"path": "ServiceRequest.meta.source"
}, {
"id": "ServiceRequest.text",
"min": 1,
"path": "ServiceRequest.text",
"mustSupport": true
}, {
"id": "ServiceRequest.identifier",
"max": "1",
"min": 1,
"path": "ServiceRequest.identifier",
"mustSupport": true
}, {
"id": "ServiceRequest.basedOn",
"path": "ServiceRequest.basedOn",
"comment": "Usage note: MA - If there is a Care plan resource created for a detailed care plan include the reference to the careplan during which this service request was created\r\n\r\nPSS - N/A\r\n\r\nReferences SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
"mustSupport": true
}, {
"id": "ServiceRequest.status",
"path": "ServiceRequest.status",
"comment": "usage note: draft, active, completed or unknown are likely status relevant\r\nPSS --> FHIR\r\nActive --> active\r\nMore Information Requested --> Active\r\nCompleted --> Completed\r\nCancelled --> revoked\r\nRequest Refused--> revoked\r\nPatient Never Went/Missed Appointment --> on-hold\r\n\r\nMA --FHIR\r\nActive -- > Active\r\nCompeleted --> completed\r\nDeleted --> entered-in-error\r\n\r\nThe status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](event.html) for general discussion) or using the [Task](task.html) resource.",
"mustSupport": true
}, {
"id": "ServiceRequest.intent",
"path": "ServiceRequest.intent",
"comment": "Usage note: Use Order as intent \r\nThis element is labeled as a modifier because the intent alters when and how the resource is actually applicable.",
"mustSupport": true
}, {
"id": "ServiceRequest.category",
"path": "ServiceRequest.category",
"comment": "108252007 Laboratory procedure \r\n363679005 Imaging\r\n44383000 Patient referral for consultation\r\n\r\nThere may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource. The level of granularity is defined by the category concepts in the value set.",
"mustSupport": true
}, {
"id": "ServiceRequest.priority",
"path": "ServiceRequest.priority",
"mustSupport": true
}, {
"id": "ServiceRequest.code",
"path": "ServiceRequest.code",
"mustSupport": true
}, {
"id": "ServiceRequest.code.text",
"path": "ServiceRequest.code.text",
"mustSupport": true
}, {
"id": "ServiceRequest.orderDetail",
"path": "ServiceRequest.orderDetail",
"comment": "In MedAccess Order detail will provide the names of the forms attached to the request\r\n\r\nFor information from the medical record intended to support the delivery of the requested services, use the `supportingInformation` element.",
"mustSupport": true
}, {
"id": "ServiceRequest.subject",
"path": "ServiceRequest.subject",
"mustSupport": true
}, {
"id": "ServiceRequest.encounter",
"path": "ServiceRequest.encounter",
"mustSupport": true
}, {
"id": "ServiceRequest.occurrence[x]",
"path": "ServiceRequest.occurrence[x]",
"comment": "Usage note: When the service is scheduled to take place when available",
"mustSupport": true
}, {
"id": "ServiceRequest.authoredOn",
"path": "ServiceRequest.authoredOn",
"mustSupport": true
}, {
"id": "ServiceRequest.requester",
"path": "ServiceRequest.requester",
"mustSupport": true
}, {
"id": "ServiceRequest.performer",
"path": "ServiceRequest.performer",
"mustSupport": true
}, {
"id": "ServiceRequest.performer.reference",
"path": "ServiceRequest.performer.reference",
"mustSupport": true
}, {
"id": "ServiceRequest.performer.display",
"path": "ServiceRequest.performer.display",
"mustSupport": true
}, {
"id": "ServiceRequest.reasonCode",
"path": "ServiceRequest.reasonCode",
"mustSupport": true
}, {
"id": "ServiceRequest.note",
"path": "ServiceRequest.note",
"comment": "Usage note: Any notes related to the service Request or the updates to the service request as additional note. \r\n\r\nFor systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. *Annotations SHOULD NOT* be used to communicate \"modifying\" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).",
"mustSupport": true
}, {
"id": "ServiceRequest.note.author[x]",
"path": "ServiceRequest.note.author[x]",
"mustSupport": true
}, {
"id": "ServiceRequest.note.time",
"path": "ServiceRequest.note.time",
"mustSupport": true
} ]
},
"baseDefinition": "http://hl7.org/fhir/StructureDefinition/ServiceRequest"
}