Intersection of https://dhp.uz/fhir/core/StructureDefinition/uz-core-specimen and https://dhp.uz/fhir/core/StructureDefinition/uz-core-specimen

This is the set of resources that conform to both UZ Core Specimen (https://dhp.uz/fhir/core/StructureDefinition/uz-core-specimen) and UZ Core Specimen (https://dhp.uz/fhir/core/StructureDefinition/uz-core-specimen).

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Specimen 0..*Sample for analysis
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: ?? (required): IETF language tag for a human language
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
Constraints: ext-1
... identifier SΣ0..*IdentifierSpecimen identifier used by the source system (e.g., LIS). Enables tracking, matching, and referencing the specimen across systems.
... accessionIdentifier SΣ0..1IdentifierLaboratory accession identifier assigned when the specimen is accepted/registered by the laboratory. Used to link the specimen to lab workflows and results.
... status ?!SΣ0..1codeCurrent lifecycle status of the specimen (e.g., available, unavailable).
Binding: ?? (required)
... type SΣ0..1CodeableConceptType of specimen (e.g., venous blood, urine, swab) used to interpret tests and processing requirements.
Binding: ?? (preferred)
... subject SΣ0..1Reference(UZ Core Patient(0.9.0) | UZ Core Location(0.9.0) | Substance | #sd-808-uz-core-patient-uz-core-patient)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.
... receivedTime SΣ0..1dateTimeDate/time the specimen was received by the laboratory/performing organization. Supports turnaround-time and traceability.
... parent S0..*Reference to the parent specimen when this specimen is derived/aliquoted from another specimen.
... request S0..*Reference(ServiceRequest)Order/request that triggered the specimen collection. Enables linking specimen to ordered tests/services.
... combined SΣ0..1codeWhether the container holds a pooled/combined specimen from multiple collection events or sources (if applicable).
Binding: ?? (required)
... role S0..*CodeableConceptRole of this container in the overall specimen . Supports lab handling and result association.
Binding: ?? (preferred)
... feature 0..*BackboneElementThe physical feature of a specimen
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... type 1..1CodeableConceptHighlighted feature
Binding: ?? (example): SNOMED CT Body site concepts
.... description 1..1stringInformation about the feature
... collection S0..1BackboneElementCollection details
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... collector SΣ0..1Reference(UZ Core Practitioner(0.9.0) | UZ Core PractitionerRole(0.9.0) | #sd-789-uz-core-practitioner-uz-core-practitioner)Person or role who collected the specimen.
.... collected[x] SΣ0..1Date/time (or period) when the specimen was collected. Used for clinical interpretation and lab timing.
..... collectedDateTimedateTime
..... collectedPeriodPeriod
.... duration SΣ0..1DurationDuration of the collection process (e.g., timed urine collection). Important for correct result calculation/interpretation.
.... quantity S0..1??, ??Amount/volume of specimen collected. Used for adequacy checks and processing requirements.
.... method S0..1CodeableConceptTechnique used to perform collection
Binding: ?? (required)
.... device 0..1CodeableReference(Device)Device used to perform collection
Binding Description: (example): The device that was used to obtain the specimen (e.g. a catheter or catheter part used to draw the blood via a central line).
.... procedure 0..1Reference(Procedure)The procedure that collects the specimen
.... bodySite S0..1CodeableReference(BodyStructure)Anatomical site from which the specimen was collected.
Binding: ?? (required)
.... fastingStatus[x] SΣ0..1Patient fasting status at collection time (or relevant clinical information affecting interpretation).
Binding: ?? (required)
..... fastingStatusCodeableConceptCodeableConcept
..... fastingStatusDurationDuration
... processing 0..*BackboneElementProcessing and processing step details
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... description 0..1stringTextual description of procedure
.... method 0..1CodeableConceptIndicates the treatment step applied to the specimen
Binding: ?? (example): Type indicating the technique used to process the specimen.
.... additive 0..*Reference(Substance)Material used in the processing step
.... time[x] 0..1Date and time of specimen processing
..... timeDateTimedateTime
..... timePeriodPeriod
... container 0..*BackboneElementDirect container of specimen (tube/slide, etc.)
.... extension 0..*ExtensionAdditional content defined by implementations
Constraints: ext-1
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
Constraints: ext-1
.... device 1..1Reference(Device)Device resource for the container
.... location 0..1Reference(Location)Where the container is
.... specimenQuantity 0..1??, ??Quantity of specimen within container
... condition Σ0..*CodeableConceptState of the specimen
Binding: ?? (extensible): Codes describing the state of the specimen.
... note 0..*AnnotationComments

doco Documentation for this format