codes and candidates, each holding code objects with system, code, display, evidences, and alternatives.
The top level
Deciding whether a medical entity should be coded is a difficult and often subjective decision. Every diagnosis, symptom, or health context in a clinical note should not be coded. For instance, a symptom should only be coded if it is not commonly associated with one of the patient’s diagnoses. A chronic condition should only be coded if it affects patient care. Therefore, two lists are returned at the top level:codes and candidates:
codescontains the medical entities that the model confidently predicts should be coded.candidatescontains entities that are clinically relevant but not strictly required; optional codes that may warrant human review.
Each code object
Each list contains several code objects. Each object represents one medical entity (condition, symptom, health context, medication, or procedure, depending on the coding system).systemis the coding system the code belongs to (e.g.icd10cm-outpatient,cpt).codeis the code that best describes the entity.displayis the name of that code (often called code description).evidencescontains all the spans of text where the medical entity is mentioned. Each evidence object includescontextIndex(the index of the context item in your request array),text(the relevant text snippet), andstart/end(0-based character offsets into the context text, inclusive and exclusive respectively).alternativescontains other codes that could also describe the medical entity — codes the system considered but deemed less relevant than the one incode.
Please contact us if you have questions about the response structure or need help interpreting code predictions.