TEMPLATE test multiple categories (test multiple categories)

TEMPLATE ID	test multiple categories
Concept	test multiple categories
Description	Not Specified
Purpose	Not Specified
References
Other Details (Language Independent)	MetaDataSet:Sample Set : Template metadata sample set
Language used	en
Citeable Identifier	1013.26.1040
Root archetype id	openEHR-EHR-COMPOSITION.care_plan.v0
Care plan	Care plan: A persistent and managed list of any combination of archetypes that will support the accurate recording of a Care plan.
Laboratory test result	Laboratory test result: The result, including findings and the laboratory's interpretation, of an investigation performed on specimens collected from an individual or related to that individual.
Data
Any event	Any event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
Test name	Test name: Name of the laboratory investigation performed on the specimen(s). A test result may be for a single analyte, or a group of items, including panel tests. It is strongly recommended that 'Test name' be coded with a terminology, for example LOINC or SNOMED CT. For example: 'Glucose', 'Urea and Electrolytes', 'Swab', 'Cortisol (am)', 'Potassium in perspiration' or 'Melanoma histopathology'. The name may sometimes include specimen type and patient state, for example 'Fasting blood glucose' or include other information, as 'Potassium (PNA blood gas)'.
Overall test status	Overall test status: The status of the laboratory test result as a whole. The values have been specifically chosen to match those in the HL7 FHIR Diagnostic report, historically derived from HL7v2 practice. Other local codes/terms can be used via the Text 'choice'. This element is multiple occurrence to cater for the use cases where statuses for different aspects of the result have been split into several elements. Coded Text Registered Partial Preliminary Final Amended Corrected Appended Cancelled Entered in error Text
Overall test status timestamp	Overall test status timestamp: The date and/or time that ‘Overall test status’ was issued.
Diagnostic service category	Diagnostic service category: The diagnostic service or discipline that is responsible for the laboratory test result. This is intended to be a general categorisation and not to capture the organisational name of the laboratory. For example: anatomical pathology, immunology and transfusion medicine, medical microbiology, clinical pharmacology, medical genetics, medical biochemistry. Alternatively more granular sub categories or sub disciplines, such as endocrinology, haematology, and allergology services, may be used. This may assist clinicians in filtering between categories of results. Coding with a terminology is desirable, where possible.
Clinical information provided	Clinical information provided: Description of clinical information available at the time of interpretation of results. This data element may include a link to the original clinical information provided in the test request.
Conclusion	Conclusion: Narrative description of the key findings. For example: 'Pattern suggests significant renal impairment'. The content of the conclusion will vary, depending on the investigation performed. This conclusion should be aligned with the coded 'Test diagnosis'.
Test diagnosis	Test diagnosis: Single word, phrase or brief description that represents the clinical meaning and significance of the laboratory test result. For example: 'Severe hepatic impairment', 'Salmonella contamination'. Coding of the diagnosis with a terminology is strongly recommended, where possible. This diagnosis should be aligned with the narrative in the 'Conclusion'.
Comment	Comment: Additional narrative about the test result not captured in other fields.
State
Confounding factors	Confounding factors: Issues or circumstances that impact on the accurate interpretation of the measurement or test result. 'Confounding factors' should be reserved for uncontrolled/unplanned issues of patient state/physiology that might affect interpretation, for example 'recent exercise' or 'recent tobacco smoking'. Known or required preconditions, such as 'fasting' should be carried in the 'Sampling conditions' element within the CLUSTER.specimen archetype . In some cases preconditions are captured as part of the test name, for example 'Fasting blood glucose'. Known issues with specimen collection or handling, such as 'prolonged use of tourniquet' or 'sample haemolysed', should be carried in the 'Specimen quality' elements within CLUSTER.specimen archetype. Coding with a terminology is desirable, where possible.
Protocol
Laboratory internal identifier	Laboratory internal identifier: A local identifier assigned by the receiving Laboratory Information System (LIS) to track the test process. This identifier is an internal tracking number assigned by the LIS, and it not intended to be the name of the test. Identifier Text
Test request details	Test request details: Details about the test request. In most situations there is one test request and a single corresponding test result, however this repeating cluster allows for the situation where there may be multiple test requests reported using a single test result. As an example: 'a clinician asks for blood glucose in one request and Urea/electrolytes in a second request, but the lab analyser does both and the lab wishes to report these together'.
Original test requested name	Original test requested name: Name of the original laboratory test requested. This data element is to be used when the test requested differs from the test actually performed by the laboratory.
Requester order identifier	Requester order identifier: The local identifier assigned by the requesting clinical system. Equivalent to the HL7 Placer Order Identifier. Identifier Text
Receiver order identifier	Receiver order identifier: The local identifier assigned to the test order by the order filler, usually by the Laboratory Information System (LIS). Assigning an identifier to a request by the Laboratory lnformation System (LIS) enables tracking progress of the request and enables linking results to requests. It also provides a reference to assist with enquiries and it is usually equivalent to the HL7 Filler Order Identifier. Identifier Text
Point-of-care test	Point-of-care test: This indicates whether the test was performed directly at Point-of-Care (POCT) as opposed to a formal result from a laboratory or other service delivery organisation. True if the test was performed directly at Point-of-Care (POCT).