HL7 FHIR Implementation Guide: Breast Cancer Data, Release 1 - US Realm (Draft for Comment 2)

BreastSpecimenProfile

Definitions for oncology-BreastSpecimen.

1. Specimen:oncology-BreastSpecimen
Definition

Specimen resulting from biopsy or excision of breast and surrounding tissue.

Control0..*
InvariantsDefined on this element
dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative (: contained.text.empty())
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty())
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource (: contained.where(('#'+id in %resource.descendants().reference).not()).empty())
dom-4: 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())
2. Specimen:oncology-BreastSpecimen.id
Definition

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Control0..1
Typeid
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.

3. Specimen:oncology-BreastSpecimen.meta
Definition

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

Control0..1
TypeMeta
4. Specimen:oncology-BreastSpecimen.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.

Control0..1
Typeuri
Is Modifiertrue
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.

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.

5. Specimen:oncology-BreastSpecimen.language
Definition

The base language in which the resource is written.

Control0..1
BindingA human language.
The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable
Max Binding: All Languages
Typecode
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).

6. Specimen:oncology-BreastSpecimen.text
Definition

A human-readable narrative that contains a summary of the resource, and may 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.

Control0..1 This element is affected by the following invariants: dom-1
TypeNarrative
Alternate Namesnarrative, 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 in formation is added later.

7. Specimen:oncology-BreastSpecimen.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.

Control0..*
TypeResource
Alternate Namesinline 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.

8. Specimen:oncology-BreastSpecimen.extension
Definition

May be used to represent additional information that is not part of the basic definition of the resource. In order 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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

9. Specimen:oncology-BreastSpecimen.extension:collectiontime
Definition

When the sample was obtained, as a specific time or time period.

Control0..1
TypeExtension(CollectionTimeExtension) (Extension Type: Choice of: dateTime, Period)
10. Specimen:oncology-BreastSpecimen.extension:specimentreatment
Definition

Treatment performed on the specimen.

Control0..*
TypeExtension(SpecimenTreatmentExtension) (Extension Type: Reference(SpecimenTreatmentProfile))
11. Specimen:oncology-BreastSpecimen.extension:handlingrisk
Definition

Cautions on the handling of this specimen.

Control0..*
TypeExtension(HandlingRiskExtension) (Extension Type: CodeableConcept)
12. Specimen:oncology-BreastSpecimen.extension:specialhandling
Definition

Information about the proper handling of the specimen.

Control0..*
TypeExtension(SpecialHandlingExtension) (Extension Type: CodeableConcept)
13. Specimen:oncology-BreastSpecimen.extension:tumoridentifier
Definition

A human-readable identifier for the lesion; e.g., a letter or integer.

Control0..*
TypeExtension(TumorIdentifierExtension) (Extension Type: string)
14. Specimen:oncology-BreastSpecimen.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. Usually modifier elements provide negation or qualification. In order 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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, 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.

15. Specimen:oncology-BreastSpecimen.identifier
Definition

Id for specimen.

NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
16. Specimen:oncology-BreastSpecimen.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.

Control0..1
TypeIdentifier(AccessionIdentifierProfile)
17. Specimen:oncology-BreastSpecimen.status
Definition

The availability of the specimen.

Control0..1
BindingCodes providing the status/availability of a specimen.
The codes SHALL be taken from SpecimenStatus
Typecode
Is Modifiertrue
Comments

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

18. Specimen:oncology-BreastSpecimen.type
Definition

The kind of material that forms the specimen.

Control1..1
BindingThe codes SHALL be taken from BC BreastSpecimenTypeVS ValueSet
TypeCodeableConcept
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.

19. Specimen:oncology-BreastSpecimen.subject
Definition

Where the specimen came from. This may be from the patient(s) or from the environment or a device.

Control1..1
TypeReference(US Core Patient Profile | GroupProfile | US Core Device Profile | SubstanceProfile)
Requirements

Must know the subject context.

20. Specimen:oncology-BreastSpecimen.receivedTime
Definition

Time when specimen was received for processing or testing.

Control0..1
TypedateTime
21. Specimen:oncology-BreastSpecimen.parent
Definition

Reference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen.

Control0..1
TypeReference(BreastSpecimenProfile)
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.

22. Specimen:oncology-BreastSpecimen.request
Definition

Details concerning a test or procedure request that required a specimen to be collected.

Control0..*
TypeReference(ProcedureRequest)
Comments

The request may be explicit or implied such with a ProcedureRequest that requires a blood draw.

23. Specimen:oncology-BreastSpecimen.collection
Definition

Details concerning the specimen collection.

Control0..1
TypeBackboneElement
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
24. Specimen:oncology-BreastSpecimen.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.

Control0..1
Typestring
25. Specimen:oncology-BreastSpecimen.collection.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order 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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

26. Specimen:oncology-BreastSpecimen.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 that contains it. Usually modifier elements provide negation or qualification. In order 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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, user content, modifiers
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.

27. Specimen:oncology-BreastSpecimen.collection.collector
Definition

Person who collected the specimen.

Control0..1
TypeReference(Practitioner)
28. Specimen:oncology-BreastSpecimen.collection.collected[x]
Definition

Time when specimen was collected from subject - the physiologically relevant time.

Control0..1
TypeChoice of: dateTime, Period
[x] NoteSee Choice of Data Types for further information about how to use [x]
29. Specimen:oncology-BreastSpecimen.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.

Control0..1
TypeQuantity(SimpleQuantity)
30. Specimen:oncology-BreastSpecimen.collection.method
Definition

A coded value specifying the technique that is used to perform the procedure.

Control0..1
BindingThe codes SHALL be taken from BC BreastSpecimenCollectionMethodVS ValueSet
TypeCodeableConcept
31. Specimen:oncology-BreastSpecimen.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.

Control0..1
BindingThe codes SHALL be taken from BC BreastSiteVS ValueSet
TypeCodeableConcept
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 body-site-instance.

32. Specimen:oncology-BreastSpecimen.processing
Definition

Details concerning processing and processing steps for the specimen.

Control0..*
TypeBackboneElement
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
33. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime
Definition

The time period between the chilling of a tissue or tissue sample and the time it is warmed. CIMI Alignment: In CIMI Version 0.0.4, specimen processing is represented as a 'SpecimenProcessingPerformed' clinical statement, mapped to FHIR Procedure. However, specimen processing maps to FHIR Specimen.processing, part of the Specimen resource. It would be a difficult mapping exercise (and beyond the scope of this IG) to express the mapping rule that any CIMI SpecimenProcessingPerformed clinical statement needs to mapped to FHIR by (1) finding the corresponding Specimen entity, and (2) mapping the content of (possibly multiple) SpecimenProcessingPerformed into the FHIR Specimen resource. To avoid this complexity, the breast cancer model expresses the cold ischemia time as an attribute of the BreastSpecimen rather than a separate procedure.

Control0..1
TypeBackboneElement
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
34. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
35. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order 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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

36. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.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 that contains it. Usually modifier elements provide negation or qualification. In order 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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, user content, modifiers
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.

37. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.description
Definition

Textual description of procedure.

Control0..1
Typestring
38. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure
Definition

A coded value specifying the procedure used to process the specimen.

Control0..1
BindingType indicating the technique used to process the specimen
For example codes, see SpecimenProcessingProcedure
TypeCodeableConcept
39. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
40. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order 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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

41. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding
Definition

A reference to a code defined by a terminology system.

Control1..*
TypeCoding
Requirements

Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings.

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.

42. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding:Fixed_44778-9
Definition

Cold ischemic time {Organ}

Control1..1
TypeCoding
43. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding:Fixed_44778-9.id
Definition

unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
44. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding:Fixed_44778-9.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order 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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

45. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding:Fixed_44778-9.system
Definition

The identification of the code system that defines the meaning of the symbol in the code.

Control0..1
Typeuri
Requirements

Need to be unambiguous about the source of the definition of the symbol.

Comments

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously.

Fixed Valuehttp://loinc.org
46. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding:Fixed_44778-9.version
Definition

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

NoteThis is a business versionId, not a resource version id (see discussion)
Control0..1
Typestring
Comments

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

47. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding:Fixed_44778-9.code
Definition

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Control0..1
Typecode
Requirements

Need to refer to a particular code in the system.

Fixed Value44778-9
48. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding:Fixed_44778-9.display
Definition

A representation of the meaning of the code in the system, following the rules of the system.

Control0..1
Typestring
Requirements

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

49. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.coding:Fixed_44778-9.userSelected
Definition

Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays).

Control0..1
Typeboolean
Requirements

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Comments

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

50. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.procedure.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.

Control0..1
Typestring
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.

51. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.additive
Definition

Material used in the processing step.

Control0..0
TypeReference(Substance)
52. Specimen:oncology-BreastSpecimen.processing:oncology-ColdIschemiaTime.timePeriod
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.

Control0..1
TypePeriod
53. Specimen:oncology-BreastSpecimen.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.

Control0..*
TypeBackboneElement
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
54. Specimen:oncology-BreastSpecimen.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.

Control0..1
Typestring
55. Specimen:oncology-BreastSpecimen.container.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. In order 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.

Control0..*
TypeExtension
Alternate Namesextensions, 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.

56. Specimen:oncology-BreastSpecimen.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 that contains it. Usually modifier elements provide negation or qualification. In order 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.

Control0..*
TypeExtension
Is Modifiertrue
Alternate Namesextensions, user content, modifiers
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.

57. Specimen:oncology-BreastSpecimen.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.

NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..*
TypeIdentifier(IdentifierProfile)
58. Specimen:oncology-BreastSpecimen.container.description
Definition

Textual description of the container.

Control0..1
Typestring
59. Specimen:oncology-BreastSpecimen.container.type
Definition

The type of container associated with the specimen (e.g. slide, aliquot, etc.).

Control0..1
BindingType of specimen container
For example codes, see SpecimenContainer
TypeCodeableConcept
60. Specimen:oncology-BreastSpecimen.container.capacity
Definition

The capacity (volume or other measure) the container may contain.

Control0..1
TypeQuantity(SimpleQuantity)
61. Specimen:oncology-BreastSpecimen.container.specimenQuantity
Definition

The quantity of specimen in the container; may be volume, dimensions, or other appropriate measurements, depending on the specimen type.

Control0..1
TypeQuantity(SimpleQuantity)
62. Specimen:oncology-BreastSpecimen.container.additive[x]
Definition

Introduced substance to preserve, maintain or enhance the specimen. Examples: Formalin, Citrate, EDTA.

Control0..1
BindingSubstance added to specimen container
For example codes, see v2 Additive/Preservative
TypeChoice of: CodeableConcept, Reference(SubstanceProfile)
[x] NoteSee Choice of Data Types for further information about how to use [x]
63. Specimen:oncology-BreastSpecimen.note
Definition

To communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen).

Control0..*
TypeAnnotation