description: 'Some referral processes may ask the referrer to provide some data that impacts the performer''s automated referral processing rules. The rules for how a performer processes their referrals can be unique to the performer. Some examples include routing based on:  \n - The type of referrer (from the hospital, primary care, out of province, etc...) \n - The patient''s Postal Code FSA (e.g., K8N, L0L, etc...)  \n - The first letter of the patient''s last name (e.g., A-J, K-Z)  To handle this, use this extension, which is included in both the ServiceRequest AND MessageHeader (for add-service-request event) resources. By also including the extension in the MessageHeader, it makes it easier for implementers to find the key routing-related data fields without needing to dig further into the referral payload. \n\n  **Note**: When the eReferral process is combined with a service directory, the directory should be able to publish the valueSet of referral options that are available for a selected service.'
package_name: ca.infoway.io.erec
derivation: constraint
name: RoutingOptions
type: Extension
elements:
  extension: {index: 0}
  url:
    pattern: {type: Uri, value: 'http://fhir.infoway-inforoute.ca/io/CA-eReC/StructureDefinition/Routing-Options-EXT'}
    index: 1
  value:
    choices: [valueCodeableConcept]
    index: 3
  valueCodeableConcept: {type: CodeableConcept, choiceOf: value, index: 4}
package_version: 1.1.0-dft
extensions: {}
class: extension
kind: complex-type
url: http://fhir.infoway-inforoute.ca/io/CA-eReC/StructureDefinition/Routing-Options-EXT
base: http://hl7.org/fhir/StructureDefinition/Extension
version: null