- This version of the UK Core is a development copy.
- This contains BREAKING CHANGES as a result of the C&TA Sprint 7 Review, and STU2 Sequence ballot reconciliation.
- This version is not yet reviewed for implementation. Other versions are available on the UK Core Version History Guide
- Please follow the guidance on the Contact Us page if you need any assistance.
- A summary of changes is available on the STU3 Sequence Change Log
StructureDefinition UKCore-Specimen
Canonical_URL | Status | Current_Version | Last_Updated | Description |
---|---|---|---|---|
https://fhir.hl7.org.uk/StructureDefinition/UKCore-Specimen | active | 2.4.0 | 2023-12-12 | This profile defines the UK constraints and extensions on the International FHIR resource Specimen. |
Profile_Purpose |
---|
This profile allows the exchange of information about a sample to be used for analysis. |
Detailed Descriptions
Specimen | |
Definition | A sample to be used for analysis. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
Specimen.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
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. |
Specimen.meta | |
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. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
Mappings |
|
Specimen.implicitRules | |
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. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Specimen.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
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). |
Invariants |
|
Mappings |
|
Specimen.text | |
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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
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. |
Invariants |
|
Mappings |
|
Specimen.contained | |
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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
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. |
Mappings |
|
Specimen.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.extension:sampleCategory | |
Definition | This extension allows the recording of the category of a sample for use within Genomics, whether it is a tumour or germline sample. |
Cardinality | 0...1 |
Type | Extension(CodeableConcept) |
Alias | extensions, user content |
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. |
Invariants |
|
Mappings |
|
Specimen.modifierExtension | |
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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.identifier | |
Definition | Id for specimen. |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Invariants |
|
Mappings |
|
Specimen.accessionIdentifier | |
Definition | The identifier assigned by the lab when accessioning specimen(s). This is not necessarily the same as the specimen identifier, depending on local lab procedures. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Invariants |
|
Mappings |
|
Specimen.status | |
Definition | The availability of the specimen. |
Cardinality | 0...1 |
Type | code |
Binding | Codes providing the status/availability of a specimen. |
Must Support | True |
Modifier | True |
Summary | True |
Comments | This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. |
Invariants |
|
Mappings |
|
Specimen.type | |
Definition | The kind of material that forms the specimen. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A code from the SNOMED CT UK Clinical Terminology coding system |
Must Support | True |
Summary | True |
Comments | The type can change the way that a specimen is handled and drives what kind of analyses can properly be performed on the specimen. It is frequently used in diagnostic work flow decision making systems. |
Invariants |
|
Mappings |
|
Specimen.subject | |
Definition | Where the specimen came from. This may be from patient(s), from a location (e.g., the source of an environmental sample), or a sampling of a substance or a device. |
Cardinality | 0...1 |
Type | Reference(Patient | Group | Device | Substance | Location) |
Must Support | True |
Summary | True |
Requirements | Must know the subject context. |
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. |
Invariants |
|
Mappings |
|
Specimen.receivedTime | |
Definition | Time when specimen was received for processing or testing. |
Cardinality | 0...1 |
Type | dateTime |
Must Support | True |
Summary | True |
Invariants |
|
Mappings |
|
Specimen.parent | |
Definition | Reference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen. |
Cardinality | 0...* |
Type | Reference(Specimen) |
Comments | The parent specimen could be the source from which the current specimen is derived by some processing step (e.g. an aliquot or isolate or extracted nucleic acids from clinical samples) or one of many specimens that were combined to create a pooled sample. |
Invariants |
|
Mappings |
|
Specimen.request | |
Definition | Details concerning a service request that required a specimen to be collected. |
Cardinality | 0...* |
Type | Reference(ServiceRequest) |
Comments | The request may be explicit or implied such with a ServiceRequest that requires a blood draw. |
Invariants |
|
Mappings |
|
Specimen.collection | |
Definition | Details concerning the specimen collection. |
Cardinality | 0...1 |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Specimen.collection.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Specimen.collection.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.collection.extension:specialHandling | |
Definition | Special handling during the collection, transport, or storage of the specimen. |
Cardinality | 0...* |
Type | Extension(CodeableConcept) |
Alias | extensions, user content |
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. |
Invariants |
|
Mappings |
|
Specimen.collection.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element'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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
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. |
Invariants |
|
Mappings |
|
Specimen.collection.collector | |
Definition | Person who collected the specimen. |
Cardinality | 0...1 |
Type | Reference(Practitioner | PractitionerRole) |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Specimen.collection.collector.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Specimen.collection.collector.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.collection.collector.extension:collectionCollectorR5 | |
Definition | Person who collected the specimen. This is an R5 backport |
Cardinality | 0...1 |
Type | Extension(Reference(Patient | RelatedPerson)) |
Alias | extensions, user content |
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. |
Invariants |
|
Mappings |
|
Specimen.collection.collector.extension:collectionCollectorR5.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Specimen.collection.collector.extension:collectionCollectorR5.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.collection.collector.extension:collectionCollectorR5.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.collection.collector |
Mappings |
|
Specimen.collection.collector.extension:collectionCollectorR5.value[x] | |
Definition | Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list). |
Cardinality | 1...1 |
Type | Reference(Patient | RelatedPerson) |
Invariants |
|
Mappings |
|
Specimen.collection.collector.reference | |
Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. |
Invariants |
|
Mappings |
|
Specimen.collection.collector.type | |
Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). |
Cardinality | 0...1 |
Type | uri |
Binding | Aa resource (or, for logical models, the URI of the logical model). |
Summary | True |
Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. |
Invariants |
|
Mappings |
|
Specimen.collection.collector.identifier | |
Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. |
Cardinality | 0...1 |
Type | Identifier |
Summary | True |
Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). |
Invariants |
|
Mappings |
|
Specimen.collection.collector.display | |
Definition | Plain text narrative that identifies the resource in addition to the resource reference. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
Invariants |
|
Mappings |
|
Specimen.collection.collected[x] | |
Definition | Time when specimen was collected from subject - the physiologically relevant time. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Invariants |
|
Mappings |
|
Specimen.collection.duration | |
Definition | The span of time over which the collection of a specimen occurred. |
Cardinality | 0...1 |
Type | Duration |
Summary | True |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
Specimen.collection.quantity | |
Definition | The quantity of specimen collected; for instance the volume of a blood sample, or the physical measurement of an anatomic pathology sample. |
Cardinality | 0...1 |
Type | SimpleQuantity |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
Specimen.collection.method | |
Definition | A coded value specifying the technique that is used to perform the procedure. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | The technique that is used to perform the procedure. |
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. |
Invariants |
|
Mappings |
|
Specimen.collection.bodySite | |
Definition | Anatomical location from which the specimen was collected (if subject is a patient). This is the target site. This element is not used for environmental specimens. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Codes describing anatomical locations. May include laterality. |
Comments | 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 bodySite. |
Invariants |
|
Mappings |
|
Specimen.collection.bodySite.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Specimen.collection.bodySite.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.collection.bodySite.extension:bodySiteReference | |
Definition | An extension to replicate the changes within R5 altering the data type of Specimen.collection.bodySite from CodeableConcept to CodeableReference (bodyStructure). |
Cardinality | 0...1 |
Type | Extension(Reference(BodyStructure)) |
Alias | extensions, user content |
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. |
Invariants |
|
Mappings |
|
Specimen.collection.bodySite.extension:bodySiteReference.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Specimen.collection.bodySite.extension:bodySiteReference.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.collection.bodySite.extension:bodySiteReference.url | |
Definition | Source of the definition for the extension code - a logical name or a URL. |
Cardinality | 1...1 |
Type | uri |
Comments | The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. |
Fixed Value | https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-BodySiteReference |
Mappings |
|
Specimen.collection.bodySite.extension:bodySiteReference.value[x] | |
Definition | Value of extension - must be one of a constrained set of the data types (see [Extensibility](extensibility.html) for a list). |
Cardinality | 1...1 |
Type | Reference(BodyStructure) |
Invariants |
|
Mappings |
|
Specimen.collection.bodySite.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Specimen.collection.bodySite.text | |
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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
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. |
Invariants |
|
Mappings |
|
Specimen.collection.fastingStatus[x] | |
Definition | Abstinence or reduction from some or all food, drink, or both, for a period of time prior to sample collection. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Codes describing the fasting status of the patient. |
Summary | True |
Requirements | Many diagnostic tests require fasting to facilitate accurate interpretation. |
Comments | Representing fasting status using this element is preferred to representing it with an observation using a 'pre-coordinated code' such as LOINC 2005-7 (Calcium [Moles/time] in 2 hour Urine --12 hours fasting), or using a component observation |
Invariants |
|
Mappings |
|
Specimen.processing | |
Definition | Details concerning processing and processing steps for the specimen. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Specimen.processing.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Specimen.processing.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.processing.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element'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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
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. |
Invariants |
|
Mappings |
|
Specimen.processing.description | |
Definition | Textual description of procedure. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Specimen.processing.procedure | |
Definition | A coded value specifying the procedure used to process the specimen. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Type indicating the technique used to process the specimen. |
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. |
Invariants |
|
Mappings |
|
Specimen.processing.additive | |
Definition | Material used in the processing step. |
Cardinality | 0...* |
Type | Reference(Substance) |
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. |
Invariants |
|
Mappings |
|
Specimen.processing.time[x] | |
Definition | A record of the time or period when the specimen processing occurred. For example the time of sample fixation or the period of time the sample was in formalin. |
Cardinality | 0...1 |
Type | dateTime |
Invariants |
|
Mappings |
|
Specimen.container | |
Definition | The container holding the specimen. The recursive nature of containers; i.e. blood in tube in tray in rack is not addressed here. |
Cardinality | 0...* |
Type | BackboneElement |
Invariants |
|
Mappings |
|
Specimen.container.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
Specimen.container.extension | |
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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
Specimen.container.extension:deviceR5 | |
Definition | The device resource for the the container holding the specimen. If the container is in a holder then the referenced device will point to a parent device. |
Cardinality | 0...1 |
Type | Extension(Reference(UKCoreDevice)) |
Alias | extensions, user content |
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. |
Invariants |
|
Mappings |
|
Specimen.container.extension:locationR5 | |
Definition | The location of the container holding the specimen. |
Cardinality | 0...1 |
Type | Extension(Reference(UKCoreLocation)) |
Alias | extensions, user content |
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. |
Invariants |
|
Mappings |
|
Specimen.container.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element'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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
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. |
Invariants |
|
Mappings |
|
Specimen.container.identifier | |
Definition | Id for container. There may be multiple; a manufacturer's bar code, lab assigned identifier, etc. The container ID may differ from the specimen id in some circumstances. |
Cardinality | 0...* |
Type | Identifier |
Summary | True |
Invariants |
|
Mappings |
|
Specimen.container.description | |
Definition | Textual description of the container. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Specimen.container.type | |
Definition | The type of container associated with the specimen (e.g. slide, aliquot, etc.). |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Type of specimen container. |
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. |
Invariants |
|
Mappings |
|
Specimen.container.capacity | |
Definition | The capacity (volume or other measure) the container may contain. |
Cardinality | 0...1 |
Type | SimpleQuantity |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
Specimen.container.specimenQuantity | |
Definition | The quantity of specimen in the container; may be volume, dimensions, or other appropriate measurements, depending on the specimen type. |
Cardinality | 0...1 |
Type | SimpleQuantity |
Comments | The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. |
Invariants |
|
Mappings |
|
Specimen.container.additive[x] | |
Definition | Introduced substance to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Substance added to specimen container. |
Invariants |
|
Mappings |
|
Specimen.condition | |
Definition | A mode or state of being that describes the nature of the specimen. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes describing the state of the specimen. |
Summary | True |
Requirements | The specimen condition can be used to assess its quality or appropriateness for a specific test. |
Comments | Specimen condition is an observation made about the specimen. It's a point-in-time assessment. It can be used to assess its quality or appropriateness for a specific test. |
Invariants |
|
Mappings |
|
Specimen.note | |
Definition | To communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen). |
Cardinality | 0...* |
Type | Annotation |
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). |
Invariants |
|
Mappings |
|
Table View
Specimen | .. | |
Specimen.extension | Extension | ..1 |
Specimen.status | .. | |
Specimen.type | .. | |
Specimen.subject | .. | |
Specimen.receivedTime | .. | |
Specimen.collection | .. | |
Specimen.collection.extension | Extension | .. |
Specimen.collection.collector | .. | |
Specimen.collection.collector.extension | Extension | ..1 |
Specimen.collection.collector.extension.value[x] | .. | |
Specimen.collection.bodySite | .. | |
Specimen.collection.bodySite.extension | Extension | ..1 |
Specimen.collection.bodySite.extension.value[x] | .. | |
Specimen.container | .. | |
Specimen.container.extension | 0.. | |
Specimen.container.extension | Extension | 0..1 |
Specimen.container.extension | Extension | 0..1 |
Specimen.container.type | .. | |
Specimen.condition | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="UKCore-Specimen" /> <url value="https://fhir.hl7.org.uk/StructureDefinition/UKCore-Specimen" /> <version value="2.4.0" /> <name value="UKCoreSpecimen" /> <title value="UK Core Specimen" /> <status value="active" /> <date value="2023-12-12" /> <publisher value="HL7 UK" /> <contact> <name value="HL7 UK" /> <telecom> <system value="email" /> <value value="ukcore@hl7.org.uk" /> <use value="work" /> <rank value="1" /> </telecom> </contact> <description value="This profile defines the UK constraints and extensions on the International FHIR resource [Specimen](https://hl7.org/fhir/R4/Specimen.html)." /> <purpose value="This profile allows the exchange of information about a sample to be used for analysis." /> <copyright value="Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html." /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Specimen" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Specimen" /> <derivation value="constraint" /> <differential> <element id="Specimen"> <path value="Specimen" /> <constraint> <key value="ukcore-spec-001" /> <severity value="error" /> <human value="There SHALL be only one reference between `collection.collector` and the extension `collectionCollectorR5`" /> <expression value="collection.collector.reference.empty() or collection.collector.extension('http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.collection.collector').empty()" /> </constraint> </element> <element id="Specimen.extension:sampleCategory"> <path value="Specimen.extension" /> <sliceName value="sampleCategory" /> <short value="An extension to record the category of a sample." /> <max value="1" /> <type> <code value="Extension" /> <profile value="https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-SampleCategory" /> </type> <isModifier value="false" /> </element> <element id="Specimen.status"> <path value="Specimen.status" /> <short value="The availability of the specimen sample." /> <mustSupport value="true" /> </element> <element id="Specimen.type"> <path value="Specimen.type" /> <short value="The kind of material that forms the specimen." /> <mustSupport value="true" /> <binding> <strength value="preferred" /> <description value="A code from the SNOMED CT UK Clinical Terminology coding system" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-SpecimenType" /> </binding> </element> <element id="Specimen.subject"> <path value="Specimen.subject" /> <short value="Where the specimen came from." /> <mustSupport value="true" /> </element> <element id="Specimen.receivedTime"> <path value="Specimen.receivedTime" /> <short value="The time when specimen was received for processing." /> <mustSupport value="true" /> </element> <element id="Specimen.collection.extension:specialHandling"> <path value="Specimen.collection.extension" /> <sliceName value="specialHandling" /> <short value="This SHOULD be included if there is a high contamination risk reason for a sample / biopsy." /> <type> <code value="Extension" /> <profile value="http://hl7.org/fhir/StructureDefinition/specimen-specialHandling" /> </type> </element> <element id="Specimen.collection.collector.extension:collectionCollectorR5"> <path value="Specimen.collection.collector.extension" /> <sliceName value="collectionCollectorR5" /> <short value="The person who collected the specimen. This is an R5 backport." /> <definition value="Person who collected the specimen. This is an R5 backport" /> <max value="1" /> <type> <code value="Extension" /> <profile value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.collection.collector" /> </type> <isModifier value="false" /> </element> <element id="Specimen.collection.collector.extension:collectionCollectorR5.value[x]"> <path value="Specimen.collection.collector.extension.value[x]" /> </element> <element id="Specimen.collection.bodySite"> <path value="Specimen.collection.bodySite" /> <binding> <strength value="preferred" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-SpecimenBodySite" /> </binding> </element> <element id="Specimen.collection.bodySite.extension:bodySiteReference"> <path value="Specimen.collection.bodySite.extension" /> <sliceName value="bodySiteReference" /> <short value="An extension to allow referencing to a BodyStructure." /> <max value="1" /> <type> <code value="Extension" /> <profile value="https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-BodySiteReference" /> </type> <isModifier value="false" /> </element> <element id="Specimen.collection.bodySite.extension:bodySiteReference.value[x]"> <path value="Specimen.collection.bodySite.extension.value[x]" /> <short value="A reference to a BodyStructure" /> </element> <element id="Specimen.container.extension"> <path value="Specimen.container.extension" /> <slicing> <discriminator> <type value="value" /> <path value="url" /> </discriminator> <rules value="open" /> </slicing> <min value="0" /> </element> <element id="Specimen.container.extension:deviceR5"> <path value="Specimen.container.extension" /> <sliceName value="deviceR5" /> <min value="0" /> <max value="1" /> <type> <code value="Extension" /> <profile value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.container.device" /> </type> </element> <element id="Specimen.container.extension:locationR5"> <path value="Specimen.container.extension" /> <sliceName value="locationR5" /> <min value="0" /> <max value="1" /> <type> <code value="Extension" /> <profile value="http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.container.location" /> </type> </element> <element id="Specimen.container.type"> <path value="Specimen.container.type" /> <binding> <strength value="preferred" /> </binding> </element> <element id="Specimen.condition"> <path value="Specimen.condition" /> <binding> <strength value="extensible" /> <valueSet value="https://fhir.hl7.org.uk/ValueSet/UKCore-BiopsyState" /> </binding> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "id": "UKCore-Specimen", "url": "https://fhir.hl7.org.uk/StructureDefinition/UKCore-Specimen", "version": "2.4.0", "name": "UKCoreSpecimen", "title": "UK Core Specimen", "status": "active", "date": "2023-12-12", "publisher": "HL7 UK", "contact": [ { "name": "HL7 UK", "telecom": [ { "system": "email", "value": "ukcore@hl7.org.uk", "use": "work", "rank": 1 } ] } ], "description": "This profile defines the UK constraints and extensions on the International FHIR resource [Specimen](https://hl7.org/fhir/R4/Specimen.html).", "purpose": "This profile allows the exchange of information about a sample to be used for analysis.", "copyright": "Copyright © 2021+ HL7 UK Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Specimen", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Specimen", "derivation": "constraint", "differential": { "element": [ { "id": "Specimen", "path": "Specimen", "constraint": [ { "key": "ukcore-spec-001", "severity": "error", "human": "There SHALL be only one reference between `collection.collector` and the extension `collectionCollectorR5`", "expression": "collection.collector.reference.empty() or collection.collector.extension('http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.collection.collector').empty()" } ] }, { "id": "Specimen.extension:sampleCategory", "path": "Specimen.extension", "sliceName": "sampleCategory", "short": "An extension to record the category of a sample.", "max": "1", "type": [ { "code": "Extension", "profile": [ "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-SampleCategory" ] } ], "isModifier": false }, { "id": "Specimen.status", "path": "Specimen.status", "short": "The availability of the specimen sample.", "mustSupport": true }, { "id": "Specimen.type", "path": "Specimen.type", "short": "The kind of material that forms the specimen.", "mustSupport": true, "binding": { "strength": "preferred", "description": "A code from the SNOMED CT UK Clinical Terminology coding system", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-SpecimenType" } }, { "id": "Specimen.subject", "path": "Specimen.subject", "short": "Where the specimen came from.", "mustSupport": true }, { "id": "Specimen.receivedTime", "path": "Specimen.receivedTime", "short": "The time when specimen was received for processing.", "mustSupport": true }, { "id": "Specimen.collection.extension:specialHandling", "path": "Specimen.collection.extension", "sliceName": "specialHandling", "short": "This SHOULD be included if there is a high contamination risk reason for a sample / biopsy.", "type": [ { "code": "Extension", "profile": [ "http://hl7.org/fhir/StructureDefinition/specimen-specialHandling" ] } ] }, { "id": "Specimen.collection.collector.extension:collectionCollectorR5", "path": "Specimen.collection.collector.extension", "sliceName": "collectionCollectorR5", "short": "The person who collected the specimen. This is an R5 backport.", "definition": "Person who collected the specimen. This is an R5 backport", "max": "1", "type": [ { "code": "Extension", "profile": [ "http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.collection.collector" ] } ], "isModifier": false }, { "id": "Specimen.collection.collector.extension:collectionCollectorR5.value[x]", "path": "Specimen.collection.collector.extension.value[x]" }, { "id": "Specimen.collection.bodySite", "path": "Specimen.collection.bodySite", "binding": { "strength": "preferred", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-SpecimenBodySite" } }, { "id": "Specimen.collection.bodySite.extension:bodySiteReference", "path": "Specimen.collection.bodySite.extension", "sliceName": "bodySiteReference", "short": "An extension to allow referencing to a BodyStructure.", "max": "1", "type": [ { "code": "Extension", "profile": [ "https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-BodySiteReference" ] } ], "isModifier": false }, { "id": "Specimen.collection.bodySite.extension:bodySiteReference.value[x]", "path": "Specimen.collection.bodySite.extension.value[x]", "short": "A reference to a BodyStructure" }, { "id": "Specimen.container.extension", "path": "Specimen.container.extension", "slicing": { "discriminator": [ { "type": "value", "path": "url" } ], "rules": "open" }, "min": 0 }, { "id": "Specimen.container.extension:deviceR5", "path": "Specimen.container.extension", "sliceName": "deviceR5", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.container.device" ] } ] }, { "id": "Specimen.container.extension:locationR5", "path": "Specimen.container.extension", "sliceName": "locationR5", "min": 0, "max": "1", "type": [ { "code": "Extension", "profile": [ "http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.container.location" ] } ] }, { "id": "Specimen.container.type", "path": "Specimen.container.type", "binding": { "strength": "preferred" } }, { "id": "Specimen.condition", "path": "Specimen.condition", "binding": { "strength": "extensible", "valueSet": "https://fhir.hl7.org.uk/ValueSet/UKCore-BiopsyState" } } ] } }
Feedback
Click here to:Report issue for UKCore-Specimen, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
Examples
Blood Specimen - An example to illustrate a blood specimen for a patient.Example UKCore-Specimen-BloodSpecimen
Composition Reference - An example to illustrate the pre-adopted R5 element via an extension, which is used to reference a Patient or RelatedPerson within Specimen.collection.collector.
Example UKCore-Extension-CollectionCollector
High Risk Specimen - An example to illustrate using the HL7 core-defined Extension specimen-specialHandling to record why a specimen should be treated as a high risk.
Example UKCore-Extension-SpecialHandling
Median Cubital Vein - An example to illustrate the extension for a referenced body site.
Example UKCore-Extension-BodySiteReference
Sample Category - An example to illustrate the extension to show the Genomics classification of a sample.
Example UKCore-Extension-SampleCategory
Urine Sample - An example to illustrate a urine specimen for a patient.
Example UKCore-Specimen-UrineSpecimen
Example Usage Scenarios
The following are example usage scenarios for the UK Core Specimen profile:
- Query for specimen information
- Exchange specimen information used in Observations and DiagnosticReport
Profile Specific Implementation Guidance:
Mandatory and Must Support Data Elements
The following elements are identified as MustSupport, and it is expected that consumers and suppliers SHALL support these as per the MustSupport Guidance.
Element | Reason |
---|---|
Specimen.status | The availability of the specimen sample. |
Specimen.type | The kind of material that forms the specimen. |
Specimen.subject | Where the specimen came from. |
Specimen.receivedTime | The time when specimen was received for processing. |
Extensions
More information about the extensions can be found using the links below.
Extension | Context | Link | Comment |
---|---|---|---|
bodySiteReference | Specimen. collection.bodySite |
Extension UKCore-BodySiteReference | An extension to replicate the changes within R5 allowing the data type of Specimen.collection.bodySite to act as a CodeableReference (BodyStructure). |
collectionCollector | Specimen. collection.collector |
Extension UKCore-SpecimenCollectionCollector | An extension to replicate the changes within R5 allowing the data type of Specimen.collection.collector to reference Patient and RelatedPerson. For more details, see Pre-adopted R5 Elements. |
sampleCategory | Specimen | Extension UKCore-SampleCategory | An extension to record the Category of a sample. |
specialHandling | Specimen.collection | HL7 core-defined Extension specimen-specialHandling | This SHOULD be included if there is a high contamination risk reason for a sample/biopsy. Note: There is no binding defined within this HL7 extension. |
Bindings (differential)
More information about the bindings to UK Core ValueSets can be found below.
Context | Strength | Link |
---|---|---|
Specimen.type | preferred | https://fhir.hl7.org.uk/ValueSet/UKCore-SpecimenType |
Specimen.collection.bodySite | preferred | https://fhir.hl7.org.uk/ValueSet/UKCore-SpecimenBodySite |
Specimen.condition | extensible | https://fhir.hl7.org.uk/ValueSet/UKCore-BiopsyState |
Specimen.extension:sampleCategory | extensible | ValueSet UKCore-SampleCategory |
Constraints (differential)
More information about the constraints on the UKCore-Specimen
profile can be found below.
Key | Severity | Expression | Human_Description |
---|---|---|---|
ukcore-spec-001 | error | collection.collector.reference.empty() or collection.collector.extension('http://hl7.org/fhir/5.0/StructureDefinition/extension-Specimen.collection.collector').empty() | There SHALL be only one reference between `collection.collector` and the extension `collectionCollectorR5` |
type
If a SNOMED CT concept from the ValueSet UKCore-SpecimenType is used, and the concept is a descendant of "105590001 | Substance", Specimen.collection.method
and Specimen.collection.bodySite
SHOULD be populated.
subject
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
- UKCore-Device (draft)
- Group Resource
- Profile UKCore-Location
- Profile UKCore-Patient
- Substance Resource
collection
Specimen.collection.collector
Where possible, it is expected that the resource being referenced SHOULD conform to one of the following UK Core profiles:
Specimen.collection.bodySite
If Specimen.collection.bodySite.coding
and Extension UKCore-BodySiteReference are both are present, they are expected to be consistent with each other - e.g. the concept is to a code for headache, and the resource reference describes a headache.
processing
It is expected that Specimen.processing
SHOULD be populated where the specimen is an extracted sample for testing, obtained from a raw sample.
note
The resource referenced in Specimen.note.authorReference
SHALL conform to one of the following:
- Profile UKCore-Organization
- Profile UKCore-Patient
- Profile UKCore-Practitioner
- Profile UKCore-RelatedPerson