FHIR Genomics Implementation Guide

Notice

Important: This guidance is under active development by NHS England and content may be added or updated on a regular basis.
This Implementation Guide is currently in Draft and SHOULD NOT be used for development or active implementation without express direction from the NHS England Genomics Unit.

StructureDefinition UKCore-ServiceRequest

Focal resource for test order messages. All additional information or resources SHOULD be linked back to the ServiceRequest or be referenced from the ServiceRequest directly.

ServiceRequests which have been updated post submission SHALL be accompanied by Provenance resources, referencing the ServiceRequest which detail when the resource was changed, who made the change and why.

An illustrative diagram of the links between ServiceRequests and other resources is provided below. Note: not all resource links are represented, to increase legibility of the diagram.

Profile url	FHIR Module	Normative Status
https://fhir.hl7.org.uk/StructureDefinition/UKCore-ServiceRequest	UKCore	trial-use

UKCoreServiceRequest (ServiceRequest)	I		ServiceRequest	There are no (further) constraints on this element Element id ServiceRequest Short description A request for a service to be performed Alternate names diagnostic request, referral, referral request, transfer of care request Definition A record of a request for service such as diagnostic investigations, treatments, or operations to be performed. Data type ServiceRequest Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource `contained.where((('#'+id in (%resource.descendants().reference \| %resource.descendants().as(canonical) \| %resource.descendants().as(uri) \| %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()` dom-6: A resource should have narrative for robust management text.`div`.exists() dom-5: If a resource is contained in another resource, it SHALL NOT have a security label `contained.meta.security.empty()` prr-1: orderDetail SHALL only be present if code is present `orderDetail.empty() or code.exists()` Mappings rim: Entity. Role, or Act workflow: Request v2: ORC rim: Act[moodCode<=INT]
id	Σ	0..1	string	There are no (further) constraints on this element Element id ServiceRequest.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type string
meta	Σ	0..1	Meta	There are no (further) constraints on this element Element id ServiceRequest.meta Short description Metadata about the resource Definition 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. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id ServiceRequest.implicitRules Short description A set of rules under which this content was created Definition 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. Comments Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
language		0..1	codeBinding	There are no (further) constraints on this element Element id ServiceRequest.language Short description Language of the resource content Definition The base language in which the resource is written. Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Data type code Binding A human language. CommonLanguages (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
text		0..1	Narrative	There are no (further) constraints on this element Element id ServiceRequest.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition 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. Comments Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. Data type Narrative Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: N/A rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id ServiceRequest.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition 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. Comments This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. Data type Resource Mappings rim: Entity. Role, or Act rim: N/A
extension	I	0..*	Extension	There are no (further) constraints on this element Element id ServiceRequest.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
sourceOfServiceRequest	I	0..1	Extension(CodeableConcept)	Element id ServiceRequest.extension:sourceOfServiceRequest Short description Describes the source of the Service Request. Alternate names extensions, user content Definition This represents the source of referral. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension(CodeableConcept) Extension URL https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-SourceOfServiceRequest Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
additionalContact	I	0..*	Extension(Reference(Organization \| Practitioner \| PractitionerRole))	Element id ServiceRequest.extension:additionalContact Short description Supports recording of additional contacts, who should be contacted regarding questions arising from the service request. This differs from the requester and responsibleClinician. Alternate names extensions, user content Definition Details of an additional contact, who should be contacted regarding questions arising from the service request. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension(Reference(Organization \| Practitioner \| PractitionerRole)) Extension URL https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-AdditionalContact Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
coverage	I	0..1	Extension(CodeableConcept)	Element id ServiceRequest.extension:coverage Short description Supports the exchange of information describing the method of funding for the Service Request. Alternate names extensions, user content Definition The funding category for the Service Request. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension(CodeableConcept) Extension URL https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-Coverage Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	?! I	0..*	Extension	There are no (further) constraints on this element Element id ServiceRequest.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition 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's 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
identifier	Σ	0..*	Identifier	There are no (further) constraints on this element Element id ServiceRequest.identifier Short description Identifiers assigned to this order Definition Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller. Comments The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2). For further discussion and examples see the resource notes section below. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier workflow: Request.identifier w5: FiveWs.identifier v2: ORC.2, ORC.3, RF1-6 / RF1-11, rim: .identifier quick: ClinicalStatement.identifier
instantiatesCanonical	Σ	0..*	canonical(ActivityDefinition \| PlanDefinition)	There are no (further) constraints on this element Element id ServiceRequest.instantiatesCanonical Short description Instantiates FHIR protocol or definition Definition The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. Comments Note: This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. Data type canonical(ActivityDefinition \| PlanDefinition) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.instantiatesCanonical v2: Varies by domain rim: .outboundRelationship[typeCode=DEFN].target
instantiatesUri	Σ	0..*	uri	There are no (further) constraints on this element Element id ServiceRequest.instantiatesUri Short description Instantiates external protocol or definition Definition The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. Comments This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.instantiatesUri v2: Varies by domain rim: .outboundRelationship[typeCode=DEFN].target
basedOn	S Σ I	0..*	Reference(CarePlan \| ServiceRequest \| MedicationRequest)	Element id ServiceRequest.basedOn Short description What the service request fulfils. Alternate names fulfills Definition Plan/proposal/order fulfilled by this request. Comments References 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. Data type Reference(CarePlan \| ServiceRequest \| MedicationRequest) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.basedOn v2: ORC.8 (plus others) rim: .outboundRelationship[typeCode=FLFS].target
replaces	Σ I	0..*	Reference(ServiceRequest)	There are no (further) constraints on this element Element id ServiceRequest.replaces Short description What request replaces Alternate names supersedes, prior, renewed order Definition The request takes the place of the referenced completed or terminated request(s). Comments References 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. Data type Reference(ServiceRequest) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.replaces v2: Handled by message location of ORC (ORC.1=RO or RU) rim: .outboundRelationship[typeCode=RPLC].target
requisition	Σ	0..1	Identifier	There are no (further) constraints on this element Element id ServiceRequest.requisition Short description Composite Request ID Alternate names grouperId, groupIdentifier Definition A shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier. Requirements Some business processes need to know if multiple items were ordered as part of the same "requisition" for billing or other purposes. Comments Requests 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. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier workflow: Request.groupIdentifier v2: ORC.4 rim: .inboundRelationship(typeCode=COMP].source[moodCode=INT].identifier
status	S Σ ?!	1..1	codeBinding	Element id ServiceRequest.status Short description The status of the order. Definition The status of the order. Comments The 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 for general discussion) or using the Task resource. Data type code Binding The status of a service order. RequestStatus (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.status w5: FiveWs.status v2: ORC.5,RF1-1 rim: .status quick: Action.currentStatus
intent	S Σ ?!	1..1	codeBinding	Element id ServiceRequest.intent Short description Whether the request is a proposal, plan, an original order or a reflex order. Definition Whether the request is a proposal, plan, an original order or a reflex order. Comments This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. Data type code Binding The kind of service request. RequestIntent (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.intent w5: FiveWs.class v2: N/A rim: .moodCode (nuances beyond PRP/PLAN/RQO would need to be elsewhere)
category	S Σ	0..*	CodeableConcept	Element id ServiceRequest.category Short description A code that classifies the service for searching, sorting and display purposes. Definition A code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). Requirements Used for filtering what service request are retrieved and displayed. Comments There 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. Data type CodeableConcept Sliced: Unordered, Open, by coding.system(Value) Binding Classification of the requested service. ServiceRequestCategoryCodes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD w5: FiveWs.class v2: RF1-5 rim: .outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="INT"].code
genomicsWholeCaseSequencing	Σ	0..*	CodeableConceptBinding	Element id ServiceRequest.category:genomicsWholeCaseSequencing Short description Classification of Genomics service Definition A code that classifies the service for Genomics, whether it is a Whole Case Genome Sequencing or non-Whole Genome Sequencing for cancer or rare diseases Requirements Used for filtering what service request are retrieved and displayed. Comments There 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. Data type CodeableConcept Binding Classification of the requested service. UKCoreGenomeSequencingCategory (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD w5: FiveWs.class v2: RF1-5 rim: .outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="INT"].code
id		0..1	string	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
coding	Σ	0..*	Coding	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for alternative encodings within a code system, and translations to other code systems. Comments Codes 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. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.coding.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.coding.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
system	Σ	0..1	uriFixed Value	Element id ServiceRequest.category:genomicsWholeCaseSequencing.coding.system Short description Identity of the terminology system Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Fixed value https://fhir.hl7.org.uk/CodeSystem/UKCore-GenomeSequencingCategory Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.coding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	Σ	0..1	code	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.coding.code Short description Symbol in syntax defined by the system Definition A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Requirements Need to refer to a particular code in the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.coding.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.coding.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id ServiceRequest.category:genomicsWholeCaseSequencing.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
priority	S Σ	0..1	codeBinding	Element id ServiceRequest.priority Short description Indicates how quickly the ServiceRequest should be addressed with respect to other requests. Definition Indicates how quickly the ServiceRequest should be addressed with respect to other requests. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Meaning when missing If missing, this task should be performed with normal priority Data type code Binding Identifies the level of importance to be assigned to actioning the request. RequestPriority (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.priority w5: FiveWs.grade v2: TQ1.9, RF1-2 rim: .priorityCode
id		0..1	string	There are no (further) constraints on this element Element id ServiceRequest.priority.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id ServiceRequest.priority.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition 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. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
priorityReason	I	0..*	Extension(CodeableConcept)	Element id ServiceRequest.priority.extension:priorityReason Short description Supports the underlying reason why a Service Request is urgent. Alternate names extensions, user content Definition A SNOMED CT concept representing the reason a Service Request is urgent Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension(CodeableConcept) Extension URL https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-PriorityReason Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
value		0..1	System.String	There are no (further) constraints on this element Element id ServiceRequest.priority.value Short description Primitive value for code Definition Primitive value for code Data type System.String Maximum string length 1048576
doNotPerform	Σ ?!	0..1	boolean	There are no (further) constraints on this element Element id ServiceRequest.doNotPerform Short description True if service/procedure should not be performed Definition Set this to true if the record is saying that the service/procedure should NOT be performed. Requirements Used for do not ambulate, do not elevate head of bed, do not flush NG tube, do not take blood pressure on a certain arm, etc. Comments In general, only the code and timeframe will be present, though occasional additional qualifiers such as body site or even performer could be included to narrow the scope of the prohibition. If the ServiceRequest.code and ServiceRequest.doNotPerform both contain negation, that will reinforce prohibition and should not have a double negative interpretation. Meaning when missing If missing, the request is a positive request e.g. "do perform" Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.doNotPerform rim: .actionNegationInd
code	S Σ	0..1	CodeableConceptBinding	Element id ServiceRequest.code Short description What is being requested/ordered. Alternate names service requested Definition A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. Comments Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example, serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code. Data type CodeableConcept Binding A set of codes that define a procedure or a procedure with explicit context. Selected from the SNOMED CT UK coding system. UKCoreProcedureCode (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Request.code w5: FiveWs.what[x] v2: PR1-3 / OBR-4 (varies by domain) rim: .code quick: Procedure.procedureCode
orderDetail	Σ I	0..*	CodeableConceptBinding	Element id ServiceRequest.orderDetail Short description Additional order information Alternate names detailed instructions Definition Additional details and instructions about the how the services are to be delivered. For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. Comments For information from the medical record intended to support the delivery of the requested services, use the `supportingInformation` element. Data type CodeableConcept Binding Codified order entry details which are based on order context. UKCoreProcedureCode (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: NTE rim: .code quick: Procedure.procedureCode
quantity[x]	Σ	0..1		There are no (further) constraints on this element Element id ServiceRequest.quantity[x] Short description Service amount Definition An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction). Requirements When ordering a service the number of service items may need to be specified separately from the the service item. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: NTE rim: .quantity
quantityQuantity			Quantity	There are no (further) constraints on this element Data type Quantity
quantityRatio			Ratio	There are no (further) constraints on this element Data type Ratio
quantityRange			Range	There are no (further) constraints on this element Data type Range
subject	S Σ I	1..1	Reference(Patient \| Group \| Location \| Device)	Element id ServiceRequest.subject Short description The individual or entity the service is ordered for. Definition On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans). Comments References 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. Data type Reference(Patient \| Group \| Location \| Device) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.subject w5: FiveWs.subject[x] v2: PID rim: .participation[typeCode=SBJ].role quick: ClinicalStatement.subject w5: FiveWs.subject
encounter	Σ I	0..1	Reference(Encounter)	There are no (further) constraints on this element Element id ServiceRequest.encounter Short description Encounter in which the request was created Alternate names context Definition An encounter that provides additional information about the healthcare context in which this request is made. Comments References 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. Data type Reference(Encounter) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.encounter w5: FiveWs.context v2: PV1 rim: .inboundRelationship(typeCode=COMP].source[classCode<=PCPR, moodCode=EVN] quick: ClinicalStatement.encounter
occurrence[x]	Σ	0..1		There are no (further) constraints on this element Element id ServiceRequest.occurrence[x] Short description When service should occur Alternate names schedule Definition The date/time at which the requested service should occur. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.occurrence[x] w5: FiveWs.planned v2: TQ1/TQ2, OBR-7/OBR-8 rim: .effectiveTime quick: Procedure.procedureSchedule
occurrenceDateTime			dateTime	There are no (further) constraints on this element Data type dateTime
occurrencePeriod			Period	There are no (further) constraints on this element Data type Period
occurrenceTiming			Timing	There are no (further) constraints on this element Data type Timing
asNeeded[x]	Σ	0..1		There are no (further) constraints on this element Element id ServiceRequest.asNeeded[x] Short description Preconditions for service Definition If a CodeableConcept is present, it indicates the pre-condition for performing the service. For example "pain", "on flare-up", etc. Binding A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc. SNOMEDCTMedicationAsNeededReasonCodes (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a rim: boolean: precondition.negationInd (inversed - so negationInd = true means asNeeded=false CodeableConcept: precondition.observationEventCriterion[code="Assertion"].value quick: Proposal.prnReason.reason
asNeededBoolean			boolean	There are no (further) constraints on this element Data type boolean
asNeededCodeableConcept			CodeableConcept	There are no (further) constraints on this element Data type CodeableConcept
authoredOn	S Σ	0..1	dateTime	Element id ServiceRequest.authoredOn Short description The date the request was signed. Alternate names orderedOn Definition When the request transitioned to being actionable. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a workflow: Request.authoredOn w5: FiveWs.recorded v2: ORC.9, RF1-7 / RF1-9 rim: .participation[typeCode=AUT].time quick: Proposal.proposedAtTime
requester	S Σ I	0..1	Reference(Practitioner \| PractitionerRole \| Organization \| Patient \| RelatedPerson \| Device)	Element id ServiceRequest.requester Short description Who / what is requesting the service Alternate names author, orderer Definition The individual who initiated the request and has responsibility for its activation. Comments This 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. Data type Reference(Practitioner \| PractitionerRole \| Organization \| Patient \| RelatedPerson \| Device) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.requester w5: FiveWs.author v2: ORC.12, PRT rim: .participation[typeCode=AUT].role quick: ClinicalStatement.statementAuthor
performerType	Σ	0..1	CodeableConcept	There are no (further) constraints on this element Element id ServiceRequest.performerType Short description Performer role Alternate names specialty Definition Desired type of performer for doing the requested service. Comments This is a role, not a participation type. In other words, does not describe the task but describes the capacity. For example, “compounding pharmacy”, “psychiatrist” or “internal referral”. Data type CodeableConcept Binding Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc. ParticipantRoles (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Request.performerType w5: FiveWs.actor v2: PRT, RF!-3 rim: .participation[typeCode=PRF].role[scoper.determinerCode=KIND].code
performer	Σ I	0..*	Reference(Practitioner \| PractitionerRole \| Organization \| CareTeam \| HealthcareService \| Patient \| Device \| RelatedPerson)	There are no (further) constraints on this element Element id ServiceRequest.performer Short description Requested performer Alternate names request recipient Definition The desired performer for doing the requested service. For example, the surgeon, dermatopathologist, endoscopist, etc. Comments If 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. Use CareTeam to represent a group of performers (for example, Practitioner A and Practitioner B). Data type Reference(Practitioner \| PractitionerRole \| Organization \| CareTeam \| HealthcareService \| Patient \| Device \| RelatedPerson) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.performer w5: FiveWs.actor v2: PRT, Practitioner: PRD-2/PRD-7 where PRD-3 = RT; Organization: PRD-10 where PRD-3 = RT rim: .participation[typeCode=PRF].role[scoper.determinerCode=INSTANCE]
locationCode	Σ	0..*	CodeableConcept	There are no (further) constraints on this element Element id ServiceRequest.locationCode Short description Requested location Definition The preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding A location type where services are delivered. v3.ServiceDeliveryLocationRoleType (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD w5: FiveWs.actor rim: .participation[typeCode=LOC].role[scoper.determinerCode=KIND].code
locationReference	Σ I	0..*	Reference(Location)	There are no (further) constraints on this element Element id ServiceRequest.locationReference Short description Requested location Definition A reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center. Comments References 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. Data type Reference(Location) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) w5: FiveWs.actor rim: .participation[typeCode=LOC].role[scoper.determinerCode=INSTANCE]
reasonCode	Σ	0..*	CodeableConceptBinding	Element id ServiceRequest.reasonCode Short description Explanation/Justification for procedure or service Definition An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes. May relate to the resources referred to in `supportingInfo`. Comments This 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. Data type CodeableConcept Binding A set of codes that define a reason for a service request. UKCoreServiceRequestReasonCode (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD workflow: Request.reasonCode w5: FiveWs.why[x] v2: ORC.16, RF1-10 rim: .reasonCode
reasonReference	Σ I	0..*	Reference(Condition \| Observation \| DiagnosticReport \| DocumentReference)	There are no (further) constraints on this element Element id ServiceRequest.reasonReference Short description Explanation/Justification for service or service Definition Indicates another resource that provides a justification for why this service is being requested. May relate to the resources referred to in `supportingInfo`. Comments This 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. To be as specific as possible, a reference to Observation or Condition should be used if available. Otherwise when referencing DiagnosticReport it should contain a finding in `DiagnosticReport.conclusion` and/or `DiagnosticReport.conclusionCode`. When using a reference to DocumentReference, the target document should contain clear findings language providing the relevant reason for this service request. Use the CodeableConcept text element in `ServiceRequest.reasonCode` if the data is free (uncoded) text as shown in the CT Scan example. Data type Reference(Condition \| Observation \| DiagnosticReport \| DocumentReference) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.reasonReference w5: FiveWs.why[x] v2: ORC.16 rim: .outboundRelationship[typeCode=RSON].target
insurance	I	0..*	Reference(Coverage \| ClaimResponse)	There are no (further) constraints on this element Element id ServiceRequest.insurance Short description Associated insurance coverage Definition Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service. Comments References 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. Data type Reference(Coverage \| ClaimResponse) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.insurance v2: IN1/IN2 rim: .outboundRelationship[typeCode=COVBY].target
supportingInfo	I	0..*	Reference(Resource)	There are no (further) constraints on this element Element id ServiceRequest.supportingInfo Short description Additional clinical information Alternate names Ask at order entry question, AOE Definition Additional clinical information about the patient or specimen that may influence the services or their interpretations. This information includes diagnosis, clinical findings and other observations. In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)". This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example, reporting the amount of inspired oxygen for blood gas measurements. Comments To represent information about how the services are to be delivered use the `instructions` element. Data type Reference(Resource) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.supportingInfo v2: Accompanying segments rim: .outboundRelationship[typeCode=PERT].target
specimen	Σ I	0..*	Reference(Specimen)	There are no (further) constraints on this element Element id ServiceRequest.specimen Short description Procedure Samples Definition One or more specimens that the laboratory procedure will use. Comments Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to. Conversely, if the request is entered first with an unknown specimen, then the Specimen resource points to the ServiceRequest. Data type Reference(Specimen) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) v2: SPM rim: .participation[typeCode=SPC].role
bodySite	Σ	0..*	CodeableConceptBinding	Element id ServiceRequest.bodySite Short description Location on Body Alternate names location Definition Anatomic location where the procedure should be performed. This is the target site. Requirements Knowing where the procedure is performed is important for tracking if multiple sites are possible. Comments Only used if not implicit in the code found in ServiceRequest.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension procedure-targetBodyStructure. Data type CodeableConcept Binding Codes describing anatomical locations. May include laterality. SNOMEDCTBodyStructures (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: SPM rim: targetSiteCode quick: Procedure.targetBodySite
note		0..*	Annotation	There are no (further) constraints on this element Element id ServiceRequest.note Short description Comments Definition Any other notes and comments made about the service request. For example, internal billing notes. Comments For 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). Data type Annotation Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: N/A rim: Act workflow: Request.note v2: NTE rim: .inboundRelationship(typeCode=SUBJ].source[classCode=ANNGEN, moodCode=EVN].value[xsi:type=ST] quick: ClinicalStatement.additionalText
patientInstruction	Σ	0..1	string	There are no (further) constraints on this element Element id ServiceRequest.patientInstruction Short description Patient or consumer-oriented instructions Definition Instructions in terms that are understood by the patient or consumer. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: NTE rim: .text
relevantHistory	I	0..*	Reference(Provenance)	There are no (further) constraints on this element Element id ServiceRequest.relevantHistory Short description Request provenance Definition Key events in the history of the request. Comments This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject. Data type Reference(Provenance) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) workflow: Request.relevantHistory v2: N/A rim: .inboundRelationship(typeCode=SUBJ].source[classCode=CACT, moodCode=EVN]

FHIR	MDS	HL7v2
ServiceRequest.requester	Requester (more details in PractitionerRole resource mappings), PLCM activity - Commissioned service category code, Previous genomic report - Original requester full name, Previous genomic report - Original requester organisation ODS code, Previous genomic report - Original requester reason for request, Previous non genomic report - Original requester full name, Previous non genomic report - Original requester organisation ODS code, Previous non genomic report - Original requester reason for request	Various ORC/STF segments
ServiceRequest.extension:additionalContact	Additional Contact (more details in PractitionerRole resource mappings)	Various STF segments
ServiceRequest.subject	Patient (more details in Patient resource mappings), Patient - Is relative	First PID segment in OML message, relatives referenced through NK1 segments
ServiceRequest.identifier	Test request - Test request id, PLCM activity - NGIS referral identifier, Previous genomic report - Report lab test number	ORC-2, ORC-3
ServiceRequest.extension:coverage	Test request - Payment status	IN1-15
ServiceRequest.authoredOn	Test request - Date and time request sent, PLCM activity - Financial month, PLCM activity - Financial year, PLCM activity - Turnaround time (calendar days)	ORC-9 (for TAT subtracted from OBR-7)
ServiceRequest.priority	Test request - Is urgent	TQ1-9
ServiceRequest.extension:priorityReason	Test request - Urgency reason	N/A could possibly use TQ1-10
ServiceRequest.code.coding.system	Test request - Test Directory version	OBR-4.3
ServiceRequest.code	Test request - CI code, Test request - CITT code, PLCM activity - Service code, PLCM activity - Point of delivery code, PLCM activity - Local point of delivery code, PLCM activity - Test method code	OBR-4
ServiceRequest.orderDetail	Test request - CI code for multipurpose CITT, Test request - Type of reanalysis, Test request - DNA storage information	NTE segment attached to OBR
ServiceRequest.reasonCode	Test request - Reason for testing, Test request - Reason for reanalysis	OBR-13 segment linked to ORC
ServiceRequest.supportingInfo	Test request - Detail of reason for reanalysis, Test request - Further information	NTE segments linked to OBR segment for reanalysis reason, Additional segments attached to ORC/OBR
ServiceRequest.occurrenceDateTime	Test request - Date report required by	OBR-8
ServiceRequest.performer	PLCM activity - ODS code of organisation commissioned to deliver requested test	PRD-7 where PRD-1=RT
ServiceRequest.note	Raw specimen/biopsy - Sample to follow reason	NTE segment attached to ORC

Propose a change to UKCore-ServiceRequest

Additional Guidance

extension:additionalContact
extension:coverage
identifier
basedOn
status
intent
category
priority
doNotPerform
code
orderDetail
subject
occurrence[x]
authoredOn
requester
performer
reasonCode
reasonReference
supportingInfo
specimen
note

extension:additionalContact

Extension used for recording additional personnel who should be contacted regarding questions related to a test order. This is separate from the requester or reporting address.

The additional contact SHOULD be a reference to a PractitionerRole resource wherever possible and SHALL contain contact details for the practitioner.

Additionally, where are there multiple practitioners involved in providing care who need to be listed as contacts, the contact details for each practitioner (or service) SHOULD be specified through additional additionalContact entries.

{
    "url": "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-AdditionalContact",
    "valueReference": {
        "reference": "PractitionerRole/PractitionerRole-AdditionalContact-Example"
    }
},

extension:coverage

SHALL be present for Genomic Order Management test orders. Extension for recording how work against the test order is being funded. The ValueSet bound to this extension is currently under review by the NHS England Genomics Informatics Working Advisory Group and subject to change.

{
    "url": "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-Coverage",
    "valueCoding": {
        "system": "https://fhir.hl7.org.uk/CodeSystem/UKCore-FundingCategory",
        "code": "nhs",
        "display": "NHS"
    }
}

identifier

Automatically assigned by the central service, though source systems MAY provide a local identifier for tracking within their own system, in which case the central order number is appended to the identifiers array.

    "identifier":  [
        {
            "system": "https://fhir.nhs.uk/Id/GMSOrder",
            "value": "ROA43728"
        }
    ],

basedOn

SHALL reference a parent request where this ServiceRequest is based on a previous request, e.g. in the case of reanalysis and cascade testing, or Germline Late tests in the Tumour First/Germline Late scenario.

"basedOn":  [
        {
            "reference": "ServiceRequest/ServiceRequest-NonWGSTestOrderForm-FatherOfFayMutlow-Example"
        }
    ],

status

SHALL be provided. ServiceRequests SHOULD be marked as 'draft' until submitted, after which they will be marked as 'active' automatically by the central GMS system.

A ServiceRequest may be marked as 'on-hold' if work against it cannot continue temporarily, e.g. due to certain prerequisite information not being provided. A ServiceRequest SHOULD be marked as 'revoked' if cancelled, either by the lab performing work against the order or at the request of the requesting clinician, though in each case a Provenance resource SHALL be provided to capture why the state change has occurred. The requesting clinician may also mark the ServiceRequest as entered-in-error, though implications for work already in progress needs to be investigated further.

A ServiceRequest SHOULD only be marked as completed by the requesting clinician upon receipt and review of the resulting DiagnosticReport.

For the full list of expected/supported ServiceRequest statuses, please see the table below:

Status	Description	Genomic workflow usage
Draft	The request has been created but is not yet complete or ready for action.	Saved but not submitted to central service (out of scope for Alpha).
Active	The request is in force and ready to be acted upon.	Submitted to central service.
On Hold	The request (and any implicit authorization to act) has been temporarily withdrawn but is expected to resume in the future.	Issue with the authorization for the test (potentially recoverable), not expected to be driven by on-hold statuses of Tasks.
Revoked	The request (and any implicit authorization to act) has been terminated prior to the known full completion of the intended actions. No further activity should occur.	Unrecoverable issue with order. Either used when the test is no longer needed or there is an is an unrecoverable failure with its fulfillment (driven by the requesting clinician). This status will propagate down to any Tasks which have not already moved into in-progress, Tasks not started will be marked with the status of cancelled.
Completed	The activity described by the request has been fully performed. No further activity will occur.	Completed order, marked by requestor once DiagnosticReport is received and accepted.
Entered in Error	This request should never have existed and should be considered 'void'. (It is possible that real-world decisions were based on it. If real-world activity has occurred, the status should be "revoked" rather than "entered-in-error".)	MAY be used for ServiceRequests created in error, can only be set if no Tasks have been started. If a Task has been moved out of its initial state, the status of Revoked SHOULD be used instead. This status will propagate down to Tasks, marking the tasks as entered-in-error.
Unknown	The authoring/source system does not know which of the status values currently applies for this request. Note: This concept is not to be used for "other" - one of the listed statuses is presumed to apply, but the authoring/source system does not know which.	Should not be used.

"status": "active",

intent

SHALL be provided. ServiceRequests SHOULD be marked as 'order' unless they have been raised by a lab in response to an existing ServiceRequest, in which case they SHOULD be marked as 'reflex-order'. For reflex orders, the ServiceRequest.basedOn field SHALL be populated with the original ServiceRequest, for traceability.

"intent": "order",

priority

ServiceRequests marked as urgent (i.e. not routine) SHOULD populate the extension:priorityReason with why an urgent test is being requested. This SHOULD ideally be coded using SNOMED CT concepts. Multiple priorityReason extensions are allowed within a single ServiceRequest in order to aid post-coordination.

"priority": "urgent",
"_priority": {
        "extension" : [ 
            {
                "url" : "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-PriorityReason",
                "valueCodeableConcept" : {
                    "coding": [
                        {
                            "system": "http://snomed.info/sct",
                            "code": "722480002",
                            "display": "Chemotherapy started"
                        }
                    ]
                }
            }
        ]
    }

doNotPerform

For the purposes of Genomic Test Ordering, the doNotPerform field SHALL NOT be used. All ServiceRequests requests received by the system will be assumed to be orders for services/testing.

code

SHALL be provided. Code SHOULD contain the CI or CITT Test Directory code, currently available at https://www.england.nhs.uk/publication/national-genomic-test-directories/. There is currently no CodeSystem or queryable API for retrieving codes but work to address this is underway within the NHS England Genomics Unit.

Codes from the Genomic Test Directory SHOULD also specify the version number of the test directory at the time the test is being ordered, to ensure the test methods used are consistent with that version of the directory.

"code": {
        "coding":  [
            {
                "system": "https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory",
                "code": "R67.2",
                "display": "Monogenic hearing loss",
                "version": "7"
            }
        ]
    },

orderDetail

If multiple codes are being requested within one Test Order, these SHOULD be represented using the 'orderDetail' field, with the main indication captured using the 'code' field above. If completely separate pathways/samples etc. are required for processing against the codes, it is expected these would be requested via multiple ServiceRequests instead of a single ServiceRequest with multiple orderDetail codes. The exact cut-off for when orderDetail vs. multiple ServiceRequest should be used is still being investigated. An appropriate code(Panel codes) SHOULD come from the following NamingSystem: England-GenomicTestPanelCode

"orderDetail": [
    {
        "coding":  [
            {
                "system": "https://fhir.nhs.uk/CodeSystem/England-GenomicTestDirectory",
                "code": "R67.1",
                "display": "Monogenic hearing loss"
            }
        ]
    }
],

subject

SHALL be provided. Reference to the associated Patient. This MAY be through a resource reference if the ID on the central service is known (or provided within the transaction bundle) or through NHS number where this is known and has been traced through PDS

"subject": {
        "reference": "Patient/Patient-MeirLieberman-Example",
        "identifier": {
            "system": "https://fhir.nhs.uk/Id/nhs-number",
            "value": "9449307873"
        }
    },

occurrence[x]

If a result is required by a specific date, this MAY be indicated though occurrenceDateTime, though there is no guarantee from the GMS that the ServiceRequest will be processed in the time frame specified.

"occurrenceDateTime": "2023-08-25",

autoredOn

SHALL be populated by the client upon submission, either manually by the user or automatically by the system integrating with the central GMS.

"authoredOn": "2023-08-05",

requester

SHALL be populated on all ServiceRequests submitted to the central GMS. This SHALL reference a PractitionerRole resource also submitted to the system (either within a single transaction or previously POSTed).

"requester": {
        "reference": "PractitionerRole/PractitionerRole-GeneSmithENT-Example"
    },

performer

Allows a requester to assign processing of the ServiceRequest to a particular organization (e.g. a remote GLH). The performer field SHOULD be populated with the ODS code for the managing organization/GLH.

In the future state, ServiceRequests may be kept open, by not specifying a performer, allowing them to be picked up by the local GLH or otherwise routed based on by test routing (TBC).

"performer": [
        {
            "identifier": {
                "system": "https://fhir.nhs.uk/Id/ods-organization-code",
                "value": "RGT01"
            }
        }
    ]

reasonCode

reasonCode SHOULD be populated with the type of request being ordered e.g. Diagnostic, Carrier, Predictive, Stored DNA etc. The final list of applicable codes which can be selected is still under review. It is expected that a fixed list of SNOMED CT codes will be permissible, to allow appropriate categorisation by the central service.

This mapping is currently under review as the CI/CITT code is also technically the reason/indication for testing.

"reasonCode":  [
        {
            "coding":  [
                {
                    "system": "http://snomed.info/sct",
                    "code": "103693007",
                    "display": "Diagnostic procedure"
                }
            ]
        }
    ],

reasonReference

Reference SHOULD be associated to the primary condition being tested for. i.e,

"reasonReference": {
        "reference": "Condition/Condition-LungTumor-Example"
    },

supportingInfo

Any clinical information provided about the patient for whom the testing is being requested SHALL be referenced though the supportingInfo field, to ensure all the information relevant to the ServiceRequest can be easily retrieved. This includes Observations, Conditions, Procedures, FamilyMemberHistories etc.

This also includes resources related to family members included as part of testing (consultands), e.g. in Duo/Trio scenarios. In this instance, RelatedPerson and Patient resource references for the consultands SHALL be added to the supportingInfo array, as well as any clinical resources related to these individuals. This is to ensure the number of participants for a given test can be calculated correctly, e.g. through counting the number of RelatedPerson resources referenced from ServiceRequest.supportingInfo plus the subject of the ServiceRequest itself (the proband).

For WGS testing, where Records of Discussion are required in order to process the test, Consent resources SHOULD also be added to the supportingInfo array once available.

"supportingInfo":  [
        {
            "reference": "Observation/Observation-DiseaseStatus-Example"
        },
        {
            "reference": "Observation/Observation-GenomicEthnicity-Example"
        },
        {
            "reference": "Observation/Observation-NoPregnancy-Example"
        },
        {
            "reference": "FamilyMemberHistory/FamilyMemberHistory-NonConsanguinousUnion-Example"
        },
        {
            "reference": "Observation/Observation-NoTransplant-Example"
        },
        {
            "reference": "Observation/Observation-NoTransfusion-Example"
        },
        {
            "reference": "Condition/Condition-HearingLoss-Example"
        },
        {
            "reference": "RelatedPerson/RelatedPerson-AliceSmithamProbandMother-Example"
        },
        {
            "reference": "Patient/Patient-PheobeSmithamMother-Example"
        },
    ],

specimen

ServiceRequests where the required samples already exist, e.g. in the case where a specimen already in storage needs to be processed, SHOULD reference these samples through the ServiceRequest.specimen field. Where samples need to be collected to support testing, these SHOULD instead reference the ServiceRequest, through Specimen.request (i.e. the service request has prompted collection of the sample), and these Specimen resources do not need to be referenced from within ServiceRequest.supportingInfo. The referenced Specimen resources SHOULD either be contained within the test order transaction bundle or already exist on the central GMS.

In the case of Reanalysis or Reinterpretation tests, Specimens related to previous ServiceRequest are not required to be added to the new test request. The links from the previous ServiceRequest can be followed to identify the Specimens that resulted in the data being reanalysed, e.g. (reanalysis) ServiceRequest.basedOn -> (prior) ServiceRequest, (prior) ServiceRequest <- (original) Specimen.request

"specimen": [
        {
            "reference": "Specimen/Specimen-BloodSerum-Example"
        }
    ],

note

Any information which cannot be readily be structured SHOULD be entered into the note field, though prolific use of the field to capture clinical information which better fits in level 3/4 FHIR resources is discouraged.

"note":  [
        {
            "text": "No family history of genomic testing"
        }
    ]