Score Chart

Scores a patient’s charted findings against the conditions (diagnoses) present in the same chart, flagging which documented findings support or relate to which conditions. Also known as clinical documentation improvement (CDI) scoring or clinical relevance scoring, the ScoreChart API (POST /Quippe/ClinicalLens/ScoreChart) takes a chart of coded entries, identifies condition (diagnosis) entries within it, uses MEDCIN prompting logic to build small/large/full lists of findings clinically associated with each condition, and annotates every non-condition finding in the chart with the conditions it supports.

Common uses include clinical documentation improvement (CDI) review, surfacing evidence in a note that justifies a billed or coded diagnosis, and highlighting findings that appear unrelated to any documented condition.

POST /Quippe/ClinicalLens/ScoreChart

The request body’s coded entries are supplied and returned via the shared CodedEntries schema (the same coded-chart shape used elsewhere in the API). For each condition entry found in the chart (or, if Sources is supplied, for each MEDCIN ID, external code, or content library item listed there instead), three MEDCIN prompt lists are built: a small list, a large list, and a full list. Every other finding in the chart is compared against these lists, and when a match is found an AssociatedFindings/Finding is appended to that finding’s entry, carrying the matched condition’s code, vocabulary, and a Score of 1, 2, or 3 indicating whether the match came from the small, large, or full prompt list respectively (lower scores indicate a tighter clinical association). Prompt lists can be overridden per condition by tagged content library items (see UseContentOverride and ContentPrefix) instead of the built-in MEDCIN prompting logic.

A finding that matches no condition’s prompt lists is left without an AssociatedFindings rather than causing an error, so callers should treat a missing element as “unrelated to any documented condition” rather than a failure. When a source entry also matches a content library item (rather than only the built-in MEDCIN logic), the finding additionally gets an AssociatedContentLibraryItems/Item identifying the matching content library item(s) by ID and name.