Generated Narrative: StructureDefinition DiagnosticsModel Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> DiagnosticsModel 0..* Base KPS.C Diagnostics #xD; category 1..1 string Diagnostics Category – clinical discipline, department, or diagnostic service #xD; diagnosticName 1..1 string Exact name or code of the diagnostic request/report (e.g. Lipid Profile) #xD; requestDate 1..1 dateTime Date and time of the diagnostic request #xD; justification 0..1 string Reason for diagnostic request, including relevant clinical notes #xD; status 1..1 code Status of the diagnostic request Binding: Diagnostic Status ValueSet (required) #xD; specimen 0..1 BackboneElement Specimen details #xD; type 1..1 string Type of material collected for analysis #xD; availabilityStatus 0..1 code Specimen availability status Binding: Specimen Availability Status ValueSet (required) #xD; imaging 0..1 BackboneElement Radiology imaging information #xD; studyType 0..1 string Type of imaging study requested (e.g. XR Lumbar spine) #xD; imagingDate 0..1 date Date when imaging was performed #xD; bodySite 0..1 string Body part observed #xD; images 0..* string References or links to image series from imaging #xD; resultsDate 0..1 dateTime Date and time of result availability #xD; performer 0..1 string Name or code of diagnostics performer (originator of result) #xD; interpreter 0..1 string Interpreter of result or validator #xD; diagnosticResults 0..* string Results from the analysis, e.g. numeric value, boolean, or description #xD; interpretation 0..1 code Interpretation of diagnostic results (e.g. normal, high, low) #xD; clinicalImpression 0..1 string Working diagnosis or clinical hypothesis based on diagnostics #xD; <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
Logical model for representing diagnostic requests, specimens, imaging, and results under the Kenya Patient Summary (KPS.C) standard.
Diagnostics Category – clinical discipline, department, or diagnostic service
Exact name or code of the diagnostic request/report (e.g. Lipid Profile)
Reason for diagnostic request, including relevant clinical notes
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")])
Extensions that cannot be ignored even if unrecognized
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).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Type of imaging study requested (e.g. XR Lumbar spine)
References or links to image series from imaging
Name or code of diagnostics performer (originator of result)
Results from the analysis, e.g. numeric value, boolean, or description
Interpretation of diagnostic results (e.g. normal, high, low)
Working diagnosis or clinical hypothesis based on diagnostics