Generated Narrative: StructureDefinition ch-lab-specimendefinition-r4 Name Flags Card. Type Description & Constraints SpecimenDefinition 0..* SpecimenDefinition Kind of specimen #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:status 1..1 code Publication status of the SpecimenDefinition URL: http://fhir.ch/ig/ch-lab-order/StructureDefinition/ch-lab-specimen-status Binding: PublicationStatus (required) #xD; extension:testingDestination 0..1 CodeableConcept Testing destination for the SpecimenDefinition URL: http://fhir.ch/ig/ch-lab-order/StructureDefinition/ch-lab-specimen-definition-testing-destination Binding: CH LAB Testing Destination (preferred) #xD; typeCollected 0..1 CodeableConcept The type of specimen to be collected Binding: CH LAB-Order Specimen Type (SNOMED CT) (extensible) #xD; typeTested #xD; type 1..1 CodeableConcept Type of intended specimen Binding: CH LAB-Order Specimen Type (SNOMED CT) (extensible) #xD; container #xD; description 0..1 string Container description (plain text) #xD; requirement 0..1 string Requirements or additional information about the specimen #xD; Documentation for this format
R4-compatible specimen definition aligned with R5 and HL7 Order Catalog model.
A kind of specimen with associated set of requirements.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
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()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
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()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
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.
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.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
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).
Text summary of the resource, for human interpretation
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.
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.
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Publication status of the SpecimenDefinition
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Testing destination for the SpecimenDefinition
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).
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.
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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Business identifier of a kind of specimen
A business identifier associated with the kind of specimen.
Preparation of the patient for specimen collection.
Checks on the patient prior specimen collection.
Time aspect of specimen collection (duration or offset).
The action to be performed for collecting the specimen.
The action to collect a type of specimen.
Specimen in container intended for testing by lab
Specimen conditioned in a container as expected by the testing laboratory.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Additional content defined by implementations
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.
Extensions that cannot be ignored even if unrecognized
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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
The kind of specimen conditioned for testing expected by lab.
The preference for this type of conditioned specimen.
Degree of preference of a type of conditioned specimen.
Types of material for specimen containers.
Kind of container associated with the kind of specimen
The type of container used to contain this kind of specimen.
From ISO 6710-2017 Table F.1 Recommended colour codes.
The textual description of the kind of container.
The capacity (volume or other measure) of this kind of container.
The minimum volume to be conditioned in the container.
Substance introduced in the kind of container to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA.
Special processing that should be applied to the container for this kind of specimen.
Requirements or additional information about the specimen
Requirements for delivery and special handling of this kind of conditioned specimen.
The usual time that a specimen of this kind is retained after the ordered tests are completed, for the purpose of additional testing.
Criterion for rejection of the specimen in its container by the laboratory.
Criterion for rejection of the specimen by laboratory.
Set of instructions for preservation/transport of the specimen at a defined temperature interval, prior the testing process.
It qualifies the interval of temperature, which characterizes an occurrence of handling. Conditions that are not related to temperature may be handled in the instruction element.
Set of handling instructions prior testing of the specimen.
The temperature interval for this set of handling instructions.
The maximum time interval of preservation of the specimen with these conditions.
Additional textual instructions for the preservation or transport of the specimen. For instance, 'Protect from light exposure'.