SpecimenCreateInput
No description
input SpecimenCreateInput {
identifier: [IdentifierCreateInput!]
accessionIdentifier: IdentifierCreateInput
status: String
type: CodeableConceptCreateInput
subject: ReferenceCreateInput
receivedTime: Date
parent: [ReferenceCreateInput!]
request: [ReferenceCreateInput!]
collection: SpecimenCollectionCreateInput
processing: [SpecimenProcessingCreateInput!]
container: [SpecimenContainerCreateInput!]
condition: [CodeableConceptCreateInput!]
note: [AnnotationCreateInput!]
text: NarrativeCreateInput
contained: [ResourceCreateInput!]
extension: [FhirExtensionCreateInput!]
modifierExtension: [FhirExtensionCreateInput!]
id: String
meta: FhirMetaCreateInput
implicitRules: Uri
language: String
}
Fields
SpecimenCreateInput.identifier ● [IdentifierCreateInput!] list input
Id for specimen.
SpecimenCreateInput.accessionIdentifier ● IdentifierCreateInput input
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.
SpecimenCreateInput.status ● String scalar
The availability of the specimen.
SpecimenCreateInput.type ● CodeableConceptCreateInput input
The kind of material that forms the specimen.
SpecimenCreateInput.subject ● ReferenceCreateInput input
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.
SpecimenCreateInput.receivedTime ● Date scalar
Time when specimen was received for processing or testing.
SpecimenCreateInput.parent ● [ReferenceCreateInput!] list input
Reference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen.
SpecimenCreateInput.request ● [ReferenceCreateInput!] list input
Details concerning a service request that required a specimen to be collected.
SpecimenCreateInput.collection ● SpecimenCollectionCreateInput input
Details concerning the specimen collection.
SpecimenCreateInput.processing ● [SpecimenProcessingCreateInput!] list input
Details concerning processing and processing steps for the specimen.
SpecimenCreateInput.container ● [SpecimenContainerCreateInput!] list input
The container holding the specimen. The recursive nature of containers; i.e. blood in tube in tray in rack is not addressed here.
SpecimenCreateInput.condition ● [CodeableConceptCreateInput!] list input
A mode or state of being that describes the nature of the specimen.
SpecimenCreateInput.note ● [AnnotationCreateInput!] list input
To communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen).
SpecimenCreateInput.text ● NarrativeCreateInput input
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.
SpecimenCreateInput.contained ● [ResourceCreateInput!] list input
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.
SpecimenCreateInput.extension ● [FhirExtensionCreateInput!] list input
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.
SpecimenCreateInput.modifierExtension ● [FhirExtensionCreateInput!] list input
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).
SpecimenCreateInput.id ● String scalar
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
SpecimenCreateInput.meta ● FhirMetaCreateInput input
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.
SpecimenCreateInput.implicitRules ● Uri scalar
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.
SpecimenCreateInput.language ● String scalar
The base language in which the resource is written.
Member Of
SpecimenCreate mutation