Clinical & administrative staff
Track every Periodic Health Assessment in your population by its workflow state, see exactly which service members need engagement or review, and work from exception-based summaries instead of unstructured chart review.
Identity and role are verified before any patient information is shown.
Choose how you'd like to verify your identity. This demonstration simulates authentication with a sample staff record.
Your identity is verified before any patient information is shown.
Select everything that applies. If you're covering more than one part, you won't have to sign in again between them — the console keeps your session across roles.
Reviewer access shows protected health information. Confirm these details are yours before anything is shown.
Part B Review · Records Reviewer
Your queue is in good shape. 12 assessments are ready for Part B review — just 3 need attention today.
Your tools
Every PHA below is shown by its workflow state — states, not scores. The Exceptions column surfaces only what needs a human; everything routine has already been prepared or filled by the system.
| Service member | Unit / Branch | PHA due | Workflow state | Engagement | Exceptions — what needs a human | Action |
|---|
Engagement escalation per policy: reminder at day 3, again at day 7, unit notified at day 10 with no member action. Orders marked "placed" were initiated automatically to MHS GENESIS when the item was identified.
Readiness is reported as states — how many PHAs sit in each workflow state and which IMR items are driving action. Percentages below describe the process (throughput, automation, escalations), not any individual's readiness.
Population tracked
412
Assigned service members with an active or upcoming PHA task
Median SM completion time
9 min
−78% vs. pre-module baseline (41 min forms + kiosk)
Completed without a visit
71%
Of PHAs closed in period · consistent with published finding that 86.7% of PHAs require no follow-up clinical action
Part B items auto-filled
84%
Median share of Part B completed by automated record actions before reviewer opens
States, not a percent-ready score. Each PHA is in exactly one state; the pipeline reads top to bottom.
Counts of members with the item in an actionable state — the fastest fix is listed with each.
Of 118 PHAs sent to members for engagement in the period.
Median time from notification to member start: 1.8 days.
Counts of members past due on the PHA itself, for unit-level follow-up.
Live from the board. Completed assessments are ready for quality review; the rest are grouped by what happens next.
Every factory reads from the Paratus Data Service — read-only from source systems, always. Each factory runs its own agent fleet, sized below and scaling with queue depth; the numbers below that describe the PHA pipeline are computed live from this console's worklist.
Validate · store · fix. Assembles each PHA's record set from the spine and holds source discrepancies for human review — never writes back to a source system.
Reach members, get them compliant. Runs the 3/7/10-day cadence, channels, and reminders — counts below are live from the worklist.
Briefs on the fly — enterprise to first sergeant. Generates from the same data the queues run on, so the brief can never disagree with the worklist.
Intelligent-agent follow-ups and scheduling — closing the loop on the engagement the other three factories create.
Agent counts and feed entries are illustrative of the operating model; pipeline counts marked live are computed from this console's notional worklist. Production access is governed by DoD authentication (CAC/PIV at AAL2) with role-based authorization. The Paratus Data Service is read-only from all source systems.
Everything here failed validation on the way in and is holding a PHA from moving forward. Fixes apply to the staging copy and routing only — source systems are never written; where the source is wrong, the fix is a routed task, not an edit.
Queue clear — all inbound data validated. New items appear here as feeds arrive.
Every member below has an open PHA waiting on them. The channel escalates automatically by phase — day 0: text → day 3: email → day 7: conversational AI (which doesn't just remind, it offers to complete the PHA with the member) → day 10: human outreach + unit notified → day 14: admin task. Guardrails on every message: no PHI, quiet hours honored, and the AI channels run under a fixed mandate — remind, help complete, or hand off. Nothing clinical.
BLUF pipeline snapshot — the daily stand-up in one card.
Members past due with escalation stage — for unit follow-up.
Cadence performance — who's responding and where it stalls.
One command's PHA picture — pick the command in ad-hoc below.
State distribution and automation share from the 30-day board.
MHA and PHA are tracked independently. Signing the PHA provider section moves this PHA to PHA Submitted — form and data route to the PHA System of Record, MHS GENESIS, and DD 2766 update.
Signing records your review and moves this PHA to Review Complete — Verifying: the system re-validates (e.g., pending labs), updates the MHA and PHA summaries, then routes to Ready for MHA & PHA.
Generated by the Reporting Factory from live console data plus the 30-day statistics board. Notional data · demonstration environment.
Exception-based summary: routine items were prepared or auto-filled by the system and are not repeated here. Full form and record detail open with the member's PHA in the module.