Profile Comparison between http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabSpecimenDefinition vs http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabSpecimenDefinition

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/SpecimenDefinition
copyright
date	2020-08-09T15:19:11+00:00	2023-07-08T20:53:25+00:00	Values Differ
description	The LabSpecimenDefinition profile constrains the SpecimenDefinition resource to represent definitions of IVD specimens attached to laboratory procedures described in catalogs of laboratory services using these procedures and specimens.
experimental
fhirVersion	4.0.1	5.0.0	Values Differ
jurisdiction
jurisdiction[0]	http://unstats.un.org/unsd/methods/m49/m49.htm#001
kind	resource
name	LabSpecimenDefinition
publisher	HL7 International - Orders and Observations Work Group
purpose	This profile only sets MustSupport on the minimal data of a SpecimenDefinition used in a laboratory compendium.
status	draft
title	Laboratory IVD Specimen Definition
type	SpecimenDefinition
url	http://hl7.org/fhir/uv/order-catalog/StructureDefinition/LabSpecimenDefinition
version	0.1.0	current	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
SpecimenDefinition		0..*	SpecimenDefinition	Kind of specimen		0..*	SpecimenDefinition	Kind of specimen	StructureDefinition LabSpecimenDefinition has a constraint that is removed in LabSpecimenDefinition and it is uncertain whether they are compatible (contained.contained.empty()) StructureDefinition LabSpecimenDefinition has a constraint that is removed in LabSpecimenDefinition and it is uncertain whether they are compatible (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()) StructureDefinition LabSpecimenDefinition has a constraint that is removed in LabSpecimenDefinition and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()) StructureDefinition LabSpecimenDefinition has a constraint that is removed in LabSpecimenDefinition and it is uncertain whether they are compatible (contained.meta.security.empty()) StructureDefinition LabSpecimenDefinition has a constraint that is removed in LabSpecimenDefinition and it is uncertain whether they are compatible (text.`div`.exists())
id	Σ	0..1	string	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact	Elements differ in 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.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.'
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	0..1	uri	A set of rules under which this content was created	Elements differ in 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.' vs '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 its narrative along with other profiles, value sets, etc.'
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (required): IETF language tag for a human language	Elements differ in binding.description: 'A human language.' vs 'IETF language tag for a human language'
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation	Elements differ in 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.' vs 'Contained resources do not have a 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.'
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources	Elements differ in 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.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.'
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations	Elements differ in 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.' vs '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 managable, 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.'
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!Σ	0..*	Extension	Extensions that cannot be ignored	Elements differ in 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).' vs '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 managable, 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).'
identifier	Σ	0..1	Identifier	Business identifier of a kind of specimen	Σ	0..1	Identifier	Business identifier	Elements differ in short: 'Business identifier of a kind of specimen' vs 'Business identifier' Elements differ in definition: 'A business identifier associated with the kind of specimen.' vs 'A business identifier assigned to this SpecimenDefinition.'
typeCollected	Σ	0..1	CodeableConcept	Kind of material to collect Binding: ?? (example): The type of the specimen to be collected.	Σ	0..1	CodeableConcept	Kind of material to collect Binding: ?? (example): The type of the specimen to be collected.
patientPreparation	Σ	0..*	CodeableConcept	Patient preparation for collection Binding: ?? (example): Checks on the patient prior specimen collection.	Σ	0..*	CodeableConcept	Patient preparation for collection Binding: ?? (example): SCT descendants of 703763000 |Precondition value (qualifier value)|	Elements differ in binding.description: 'Checks on the patient prior specimen collection.' vs 'SCT descendants of 703763000 |Precondition value (qualifier value)|'
timeAspect	Σ	0..1	string	Time aspect for collection Example General: 24 hour, 20' post charge	Σ	0..1	string	Time aspect for collection Example General: 24 hour, 20' post charge
collection	Σ	0..*	CodeableConcept	Specimen collection procedure Binding: ?? (example): The action to collect a type of specimen.	Σ	0..*	CodeableConcept	Specimen collection procedure Binding: ?? (example): SCT actions and procedures for specimen collection	Elements differ in binding.description: 'The action to collect a type of specimen.' vs 'SCT actions and procedures for specimen collection'
typeTested	S	0..*	BackboneElement	Specimen in container intended for testing by lab	S	0..*	BackboneElement	Specimen in container intended for testing by lab
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations	Elements differ in 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.' vs '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 managable, 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.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in 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).' vs '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 managable, 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).'
isDerived		0..1	boolean	Primary or secondary specimen Example General: false		0..1	boolean	Primary or secondary specimen Example General: false
type	S	0..1	CodeableConcept	Type of intended specimen Binding: ?? (example): The type of specimen conditioned in a container for lab testing.	S	0..1	CodeableConcept	Type of intended specimen Binding: ?? (example): The type of specimen conditioned in a container for lab testing.
preference		1..1	code	preferred | alternate Binding: ?? (required): Degree of preference of a type of conditioned specimen. Example General: preferred, alternate		1..1	code	preferred | alternate Binding: ?? (required): Degree of preference of a type of conditioned specimen. Example General: preferred, alternate
container		0..1	BackboneElement	The specimen's container		0..1	BackboneElement	The specimen's container
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations	Elements differ in 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.' vs '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 managable, 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.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in 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).' vs '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 managable, 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).'
material		0..1	CodeableConcept	Container material Binding: ?? (example): Types of material for specimen containers.		0..1	CodeableConcept	The material type used for the container Binding: ?? (example): SCT 32039001 |Glass|, 61088005 |Plastic|, 425620007 |Metal|	Elements differ in short: 'Container material' vs 'The material type used for the container' Elements differ in binding.description: 'Types of material for specimen containers.' vs 'SCT 32039001 |Glass|, 61088005 |Plastic|, 425620007 |Metal|'
type		0..1	CodeableConcept	Kind of container associated with the kind of specimen Binding: ?? (example): Type of specimen container.		0..1	CodeableConcept	Kind of container associated with the kind of specimen Binding: ?? (example): SCT descendants of 706041008 |Device for body fluid and tissue collection/transfer/processing (physical object)|	Elements differ in binding.description: 'Type of specimen container.' vs 'SCT descendants of 706041008 |Device for body fluid and tissue collection/transfer/processing (physical object)|'
cap		0..1	CodeableConcept	Color of container cap Binding: ?? (example): Color of the container cap.		0..1	CodeableConcept	Color of container cap Binding: ?? (example): Color of the container cap.
description		0..1	string	Container description Example General: Blue top tube with citrate		0..1	markdown	The description of the kind of container Example General: Blue top tube with citrate	Elements differ in short: 'Container description' vs 'The description of the kind of container'
capacity		0..1	??	Container capacity		0..1	??	The capacity of this kind of container	Elements differ in short: 'Container capacity' vs 'The capacity of this kind of container'
minimumVolume[x]		0..1	??, string	Minimum volume		0..1	??, string	Minimum volume
additive		0..*	BackboneElement	Additive associated with container		0..*	BackboneElement	Additive associated with container
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations	Elements differ in 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.' vs '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 managable, 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.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in 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).' vs '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 managable, 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).'
additive[x]		1..1	CodeableConcept, Reference(Substance)	Additive associated with container Binding: ?? (example): Substance added to specimen container.		1..1	CodeableConcept, Reference(SubstanceDefinition)	Additive associated with container Binding: ?? (example): Substance added to specimen container.
preparation		0..1	string	Specimen container preparation		0..1	markdown	Special processing applied to the container for this specimen type	Elements differ in short: 'Specimen container preparation' vs 'Special processing applied to the container for this specimen type'
requirement		0..1	string	Specimen requirements		0..1	markdown	Requirements for specimen delivery and special handling	Elements differ in short: 'Specimen requirements' vs 'Requirements for specimen delivery and special handling'
retentionTime		0..1	Duration	Specimen retention time		0..1	Duration	The usual time for retaining this kind of specimen	Elements differ in short: 'Specimen retention time' vs 'The usual time for retaining this kind of specimen'
rejectionCriterion		0..*	CodeableConcept	Rejection criterion Binding: ?? (example): Criterion for rejection of the specimen by laboratory.		0..*	CodeableConcept	Criterion specified for specimen rejection Binding: ?? (example): Criterion for rejection of the specimen by laboratory.	Elements differ in short: 'Rejection criterion' vs 'Criterion specified for specimen rejection'
handling		0..*	BackboneElement	Specimen handling before testing		0..*	BackboneElement	Specimen handling before testing
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations	Elements differ in 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.' vs '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 managable, 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.'
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	Elements differ in 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).' vs '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 managable, 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).'
temperatureQualifier		0..1	CodeableConcept	Temperature qualifier Binding: ?? (example): Set of handling instructions prior testing of the specimen.		0..1	CodeableConcept	Qualifies the interval of temperature Binding: ?? (example): Set of handling instructions prior testing of the specimen.	Elements differ in short: 'Temperature qualifier' vs 'Qualifies the interval of temperature'
temperatureRange		0..1	Range	Temperature range		0..1	Range	Temperature range for these handling instructions	Elements differ in short: 'Temperature range' vs 'Temperature range for these handling instructions'
maxDuration		0..1	Duration	Maximum preservation time		0..1	Duration	Maximum preservation time
instruction		0..1	string	Preservation instruction Example General: freeze within 4 hours		0..1	markdown	Preservation instruction Example General: freeze within 4 hours
singleUse						0..1	boolean	Specimen for single use only	Added this element
testingDestination						0..*	CodeableConcept	Where the specimen will be tested Binding: ?? (example): Codes specifying where the specimen will be tested.	Added this element
url					Σ	0..1	uri	Logical canonical URL to reference this SpecimenDefinition (globally unique)	Added this element
version					Σ	0..1	string	Business version of the SpecimenDefinition	Added this element
versionAlgorithm[x]					Σ	0..1	string, Coding	How to compare versions Binding: ?? (extensible)	Added this element
name					Σ	0..1	string	Name for this {{title}} (computer friendly)	Added this element
title					Σ	0..1	string	Name for this SpecimenDefinition (Human friendly)	Added this element
derivedFromCanonical					Σ	0..*	canonical(SpecimenDefinition)	Based on FHIR definition of another SpecimenDefinition	Added this element
derivedFromUri					Σ	0..*	uri	Based on external definition	Added this element
status					?!Σ	1..1	code	draft | active | retired | unknown Binding: ?? (required): Codes identifying the status of a SpecimenDefinition resource.	Added this element
experimental					Σ	0..1	boolean	If this SpecimenDefinition is not for real usage	Added this element
subject[x]					Σ	0..1	CodeableConcept, Reference(Group)	Type of subject for specimen collection	Added this element
date					Σ	0..1	dateTime	Date status first applied	Added this element
publisher					Σ	0..1	string	The name of the individual or organization that published the SpecimenDefinition	Added this element
contact					Σ	0..*	ContactDetail	Contact details for the publisher	Added this element
description						0..1	markdown	Natural language description of the SpecimenDefinition	Added this element
useContext						0..*	UsageContext	Content intends to support these contexts	Added this element
jurisdiction					ΣXD	0..*	CodeableConcept	Intended jurisdiction for this SpecimenDefinition (if applicable) Binding: ?? (extensible): Codes for country, country subdivision and region for indicating where a resource is intended to be used.	Added this element
purpose						0..1	markdown	Why this SpecimenDefinition is defined	Added this element
copyright						0..1	markdown	Use and/or publishing restrictions	Added this element
copyrightLabel						0..1	string	Copyright holder and year(s)	Added this element
approvalDate						0..1	date	When SpecimenDefinition was approved by publisher	Added this element
lastReviewDate						0..1	date	The date on which the asset content was last reviewed by the publisher	Added this element
effectivePeriod					Σ	0..1	Period	The effective date range for the SpecimenDefinition	Added this element
Documentation for this format