Details
-
Change Request
-
Status: Published (View Workflow)
-
Medium
-
Resolution: Not Persuasive with Modification
-
US Core (FHIR)
-
current
-
Cross-Group Projects
-
STU
-
Acme Lab Example
BUN Example
Blood Glucose Example
CBC Example
Erythrocytes Example
Hemoglobin Example
MCHC Example
Metabolic Panel Example
Neutrophils Example
Serum CO2 Example
Serum Calcium Example
Serum Chloride Example
Serum Creatinine Example
Serum Potassium Example
Serum Sodium Example
Serum Total Bilirubin Example
Urinalysis Example
Urine Bacteria Example
Urine Bilirubin Example
Urine Clarity Example
Urine Color Example
Urine Epi Cells Example
Urine Glucose Example
Urine Hemoglobin Example
Urine Ketone Example
Urine Leukocyte Esterase Example
Urine Nitrite Example
Urine Protein Example
Urine RBCsExample
Urine WBCsExample
Urine pH Example
Urobilinogen Example -
-
Brett Marquard / Riki Merrick : 18-2-2
-
Clarification
-
Non-substantive
Description
Lab results (Observations) are generated from analysis of specimens. Result values, reference ranges, and interpretation of results is specimen dependent.
There is no "lab result" listed for most all these lab orders and results. Exception is ACME WIle E Coyote Lipid panel which lists the individual results. Rather a code is listed which would be mapped to the actual lab result obtained from the analysis of a specimen (which is also not indicated). Code system names/terms should NOT be utilized to represent lab results or orders as they are dynamic and not static.
These critical clinical data/info appears to be missing from the US Core Lab examples. Also all panel/orders should be modeled in Service Request (CBC< Urinalysis, Metabolic Panel) and their results/observations "grouped per each pane order" in Diagnostic Report using based on. Specimen collected which may be different than specimen upon which results are obtained from the performance of lab tests should be indicated for the order and results .
Furthermore, these examples lack many CLIA requirements such as specimen info. Kindly bring all US Core lab examples into compliance so they can be implemented in compliant manner.
Attachments
Issue Links
- is duplicated by
-
FHIR-34907 Specimen Information for RBC Observation is Missing
-
- Duplicate
-
-
FHIR-34909 Discordant/Missing info in US Core lab examples
-
- Duplicate
-
- is voted on by
-
BALLOT-26963 Negative - Andrea Pitkus : 2022-Jan-FHIR US CORE R4.1 STU
- Closed
- relates to
-
FHIR-35122 Need to provide some guidance when specific code systems are to be used in ServiceRequest
-
- Published
-