{
  "description": null,
  "_filename": "profile-service-request.StructureDefinition.json",
  "package_name": "ForgePatientChart.0830",
  "date": "2022-08-12T20:30:19.0036288+00:00",
  "derivation": "constraint",
  "publisher": null,
  "fhirVersion": "4.0.1",
  "name": "ServiceRequest",
  "abstract": false,
  "type": "ServiceRequest",
  "experimental": null,
  "resourceType": "StructureDefinition",
  "title": null,
  "package_version": "0.1.0",
  "status": "draft",
  "id": "32694435-9542-4301-babf-0b0b9a9086b2",
  "kind": "resource",
  "url": "http://telus.com/fhir/patientChart/StructureDefinition/service-request",
  "version": null,
  "differential": {
    "element": [ {
      "id": "ServiceRequest.id",
      "min": 1,
      "path": "ServiceRequest.id",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.meta",
      "min": 1,
      "path": "ServiceRequest.meta",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.meta.lastUpdated",
      "min": 1,
      "path": "ServiceRequest.meta.lastUpdated",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.meta.source",
      "min": 1,
      "path": "ServiceRequest.meta.source",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.meta.profile",
      "path": "ServiceRequest.meta.profile",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.text",
      "path": "ServiceRequest.text",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.text.status",
      "path": "ServiceRequest.text.status",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.text.div",
      "path": "ServiceRequest.text.div",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.identifier",
      "path": "ServiceRequest.identifier",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.identifier.type",
      "path": "ServiceRequest.identifier.type",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.identifier.system",
      "min": 1,
      "path": "ServiceRequest.identifier.system",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.identifier.value",
      "min": 1,
      "path": "ServiceRequest.identifier.value",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.basedOn",
      "path": "ServiceRequest.basedOn",
      "comment": "Usage Note:   Must provide if this is supported and available in the sending EMR\r\nUsage 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.basedOn.reference",
      "path": "ServiceRequest.basedOn.reference",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.requisition",
      "path": "ServiceRequest.requisition",
      "comment": "Usage Note:   This is used for grouping service requests that are part of the same grouping/service request in the EMR.  This may not be supported by all implementation projects but should be considered.    This type of identifier likely doesn't exist in the EMR, but can created by the EMR for linking purposes.    Implementers should consider providing a requisition identifier in all cases.\r\n\r\nRequests are linked either by a \"basedOn\" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.requisition.system",
      "min": 1,
      "path": "ServiceRequest.requisition.system",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.requisition.value",
      "min": 1,
      "path": "ServiceRequest.requisition.value",
      "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\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.category.coding",
      "path": "ServiceRequest.category.coding",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.category.coding.system",
      "path": "ServiceRequest.category.coding.system",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.category.coding.code",
      "path": "ServiceRequest.category.coding.code",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.category.text",
      "path": "ServiceRequest.category.text",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.code",
      "min": 1,
      "path": "ServiceRequest.code",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.code.coding",
      "path": "ServiceRequest.code.coding",
      "comment": "Usage Note:   Where possible a code must be provided, though it is recognized that this is not always possible  .\r\n\r\nCodes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.code.coding.system",
      "path": "ServiceRequest.code.coding.system",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.code.coding.code",
      "path": "ServiceRequest.code.coding.code",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.code.text",
      "path": "ServiceRequest.code.text",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.subject",
      "path": "ServiceRequest.subject",
      "type": [ {
        "code": "Reference",
        "aggregation": [ "bundled" ],
        "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient", "http://hl7.org/fhir/StructureDefinition/Group" ]
      } ],
      "mustSupport": true
    }, {
      "id": "ServiceRequest.subject.reference",
      "path": "ServiceRequest.subject.reference",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.encounter",
      "path": "ServiceRequest.encounter",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.encounter.reference",
      "path": "ServiceRequest.encounter.reference",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.encounter.display",
      "path": "ServiceRequest.encounter.display",
      "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",
      "type": [ {
        "code": "Reference",
        "aggregation": [ "bundled" ],
        "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Practitioner", "http://hl7.org/fhir/StructureDefinition/PractitionerRole", "http://hl7.org/fhir/StructureDefinition/Organization" ]
      } ],
      "comment": "Usage Note:   Populate with the practitioner who requested this service\r\nThis not the dispatcher, but rather who is the authorizer.  This element is not intended to handle delegation which would generally be managed through the Provenance resource.",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.requester.reference",
      "path": "ServiceRequest.requester.reference",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.requester.display",
      "path": "ServiceRequest.requester.display",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.performer",
      "path": "ServiceRequest.performer",
      "comment": "Usage:   If this is an external request, there is often only a name and will be conveyed as display.   For internal requests, it will often be possible to reference a practitioner resource in addition to the display.\r\n\r\nIf multiple performers are present, it is interpreted as a list of *alternative* performers without any preference regardless of order.  If order of preference is needed use the [request-performerOrder extension](extension-request-performerorder.html).  Use CareTeam to represent a group of performers (for example, Practitioner A *and* Practitioner B).",
      "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",
      "comment": "Usage Note:   Support when available in the sending EMR\r\n\r\nMA - may have reason as a code or text\r\n\r\nThis element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all.   Use `CodeableConcept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](servicerequest-example-di.html).",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.reasonCode.coding",
      "path": "ServiceRequest.reasonCode.coding",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.reasonCode.coding.system",
      "path": "ServiceRequest.reasonCode.coding.system",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.reasonCode.coding.code",
      "path": "ServiceRequest.reasonCode.coding.code",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.reasonCode.coding.display",
      "path": "ServiceRequest.reasonCode.coding.display",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.reasonCode.text",
      "path": "ServiceRequest.reasonCode.text",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.supportingInfo",
      "path": "ServiceRequest.supportingInfo",
      "comment": "Usage Note:   This is only supported for some use cases, such as referrals, additional data may be available, eg a composition of the Patient Chart data that accompanyed the service request.\r\n\r\nTo represent information about how the services are to be delivered use the `instructions` element.",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.supportingInfo.reference",
      "path": "ServiceRequest.supportingInfo.reference",
      "mustSupport": true
    }, {
      "id": "ServiceRequest.supportingInfo.display",
      "path": "ServiceRequest.supportingInfo.display",
      "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
    }, {
      "id": "ServiceRequest.note.text",
      "path": "ServiceRequest.note.text",
      "mustSupport": true
    } ]
  },
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/ServiceRequest"
}