Generated Narrative: StructureDefinition PH-Specimen Language: en-US Name Flags Card. Type Description & Constraints Specimen 0..* Specimen Sample for analysis #xD; meta #xD; Slices for extension Content/Rules for all slices #xD; extension:hfRecordedDate 0..1 dateTime The recorded date indicating when the record was uploaded by the health facility. URL: https://nhdr.gov.ph/fhir/StructureDefinition/HFRecordedDate #xD; extension:hfLastUpdated 0..* dateTime The date indicating when the record was last updated by the health facility. URL: https://nhdr.gov.ph/fhir/StructureDefinition/HFLastUpdated #xD; lastUpdated 0..1 instant When the resource was uploaded to the NHDR. #xD; implicitRules 0..0 A set of rules under which this content was created #xD; language 0..0 Language of the resource content #xD; text 0..0 Text summary of the resource, for human interpretation #xD; contained 0..0 Contained, inline Resources #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:resultDate 0..* dateTime Date of result URL: https://nhdr.gov.ph/fhir/StructureDefinition/ResultDate #xD; extension:species 0..* CodeableConcept Type of species URL: https://nhdr.gov.ph/fhir/StructureDefinition/Species #xD; modifierExtension 0..0 Extension #xD; status 0..0 available | unavailable | unsatisfactory | entered-in-error #xD; type 0..1 CodeableConcept Kind of material that forms the specimen Binding: hl7VS-specimenType (required) #xD; subject 0..1 Reference(PH 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 or a device #xD; parent 0..0 Specimen from which this specimen originated #xD; request 0..0 Why the specimen was collected #xD; collection #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:dateReleased 0..* dateTime Date the specimen was released URL: https://nhdr.gov.ph/fhir/StructureDefinition/DateReleased #xD; modifierExtension 0..0 Extension #xD; collector 0..1 Reference(PH Practitioner | PH PractitionerRole) Who collected the specimen #xD; collected[x] 0..1 dateTime Collection time #xD; duration 0..0 How long it took to collect specimen #xD; bodySite 0..0 Anatomical collection site #xD; fastingStatus[x] 0..0 Whether or how long patient abstained from food and/or drink #xD; processing #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; modifierExtension 0..0 Extension #xD; description 0..0 Textual description of procedure #xD; additive 0..0 Material used in the processing step #xD; container #xD; id 0..0 Unique id for inter-element referencing #xD; extension 0..0 Extension #xD; modifierExtension 0..0 Extension #xD; identifier 0..0 Id for the container #xD; description 0..0 Textual description of the container #xD; capacity 0..0 Container volume or size #xD; additive[x] 0..0 Additive associated with container #xD; condition 0..* CodeableConcept State of the specimen Binding: hl7VS-specimenCondition (required) #xD; Documentation for this format
Used by permission of HL7 International, all rights reserved Creative Commons License
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())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
The recorded date indicating when the record was uploaded by the health facility.
The date indicating when the record was last updated by the health facility.
The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.
The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
When the resource was uploaded to the NHDR.
When the resource last changed - e.g. when the version changed.
This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http://hl7.org/fhir/R4/http.html#read) interaction.
Identifies where the resource comes from
A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](http://hl7.org/fhir/R4/provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.
In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
Profiles this resource claims to conform to
A list of profiles (references to [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](http://hl7.org/fhir/R4/structuredefinition-definitions.html#StructureDefinition.url).
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
Security Labels applied to this resource
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Security Labels from the Healthcare Privacy and Security Classification System.
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
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.
The date on which the outcome of the particular specimen was recorded.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Describes the type of species / organism [e.g. Malaria (Plasmodium falciparum, Plasmodium malariae, Plasmodium vivax, Plasmodium ovale, Plasmodium knowlesi)].
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
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.
.participation[typeCode=SBJ].act[classCode=ACSN, moodCode=EVN].id
available | unavailable | unsatisfactory | entered-in-error
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
Codes providing the status/availability of a specimen.
Kind of material that forms the specimen
The kind of material that forms the specimen.
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.
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
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.
The time when specimen was received for processing
Time when specimen was received for processing or testing.
.participation[typeCode=SBJ].act[code=SPCREC, moodCode=EVN].effectiveTime
Specimen from which this specimen originated
Reference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen.
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.
.scoper (if parent) .player.scopesRole[classCode=SPEC].player (if child)
Details concerning a service request that required a specimen to be collected.
The request may be explicit or implied such with a ServiceRequest that requires a blood draw.
Details concerning the specimen collection.
.participation[typeCode=SBJ].act[classCode=SPECCOLLECT, moodCode=EVN]
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Time when specimen was collected from subject - the physiologically relevant time.
The span of time over which the collection of a specimen occurred.
The quantity of specimen collected; for instance the volume of a blood sample, or the physical measurement of an anatomic pathology sample.
A coded value specifying the technique that is used to perform the procedure.
The technique that is used to perform the procedure.
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.
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](http://hl7.org/fhir/R4/extension-bodysite.html).
Codes describing anatomical locations. May include laterality.
Whether or how long patient abstained from food and/or drink
Abstinence or reduction from some or all food, drink, or both, for a period of time prior to sample collection.
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 ` such as `Observation.component code` = LOINC 49541-6 (Fasting status - Reported).
Many diagnostic tests require fasting to facilitate accurate interpretation.
Codes describing the fasting status of the patient.
Details concerning processing and processing steps for the specimen.
.participation[typeCode=SBJ].act[code=SPCTRT, moodCode=EVN]
Indicates the treatment step applied to the specimen
A coded value specifying the procedure used to process the specimen.
Type indicating the technique used to process the specimen.
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.
Direct container of specimen (tube/slide, etc.)
The container holding the specimen. The recursive nature of containers; i.e. blood in tube in tray in rack is not addressed here.
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.
Kind of container directly associated with specimen
The type of container associated with the specimen (e.g. slide, aliquot, etc.).
The capacity (volume or other measure) the container may contain.
one of: SAC 16, SAC17 and SAC 20, or SAC 21 and SAC 20
The quantity of specimen in the container; may be volume, dimensions, or other appropriate measurements, depending on the specimen type.
Introduced substance to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA.
A mode or state of being that describes the nature of the specimen.
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.
The specimen condition can be used to assess its quality or appropriateness for a specific test.
To communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen).
.inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="annotation"].value