Side Panel Setup
This is the launch form. The API base URL tells the Core System which Aurevia backend to query. The patient MRN selects the patient. Signal Pipe ID can be left blank to load the latest completed run.
What each section of the clinical review surface means, using Patient X as the example.
This page is not an environment comparison. It explains what the Core System is showing, why each panel exists, and how a reviewer should interpret each section. Patient X is used only as the worked example so the team can connect the UI to real generated content.
The Core System is not displaying free text alone. It is generated from structured clinical resources. For Patient X, the example run used the copied 1,744-resource dataset below.
This is the launch form. The API base URL tells the Core System which Aurevia backend to query. The patient MRN selects the patient. Signal Pipe ID can be left blank to load the latest completed run.
The top of the clinical platform shows the current patient, active run, run date, status, and encounter count. This tells reviewers exactly which generated output they are looking at.
The specialty tabs change the clinical lens. PCP is the broad longitudinal primary-care view. Cardiology, Pulmonology, Endo, Oncology, and Heme are intended to focus the same patient state through specialty-specific priorities.
This is the main review surface. It summarizes the important longitudinal patient facts and generated reasoning without requiring the reviewer to read raw FHIR resources first.
Acute, Inpatient, Outpatient, and Telehealth control which clinical context is emphasized. The same patient can need different summaries depending on whether the reviewer is in an ED, inpatient, clinic, or remote setting.
New patient, Seen before, and Know this patient control how much orientation vs reasoning the summary gives. New patient includes more retrieval context. Know this patient can focus more on what changed or what is missing.
Chief complaint chips route the brief toward the clinical question the reviewer is asking. They do not change the underlying patient; they change what gets prioritized.
This is the primary generated clinical summary. The brief should be concise, numbered, and clinically ordered. It should contain direct patient-specific facts first, then absence/gap reasoning when relevant.
Underlined/highlighted spans are evidence-backed clinical concepts. Hovering them should show the source detail, such as EHR evidence, EBM support, completion status, or why a fact was used.
Charts should render trends visually with points, axes, reference ranges where available, and hoverable evidence. Numbers is the compact table-style version for reviewers who want values quickly.
This lets the reviewer ask a grounded question against the selected patient/run. It should answer from the patient state and generated evidence, not behave like a generic web search.
The Core System turns the selected patient run into a compact clinical review surface: choose the specialty, encounter context, familiarity level, and chief complaint, then review the generated longitudinal brief, hoverable evidence, charts, and grounded patient-state query answers.