Praxis Async

Engineering design document

02 / 08
Part 02Questions & assumptions

Before designing the system, align on the decisions that change it.

These six questions establish ownership, data guarantees, autonomy, safety boundaries and the definition of success.

Design question

01

Panel and ownership

“Is the 1,200-patient panel owned by one clinician or shared across a care team? When Praxis identifies work, who is responsible for completing it?”

Design question

02

Data and freshness

“Which sources can Praxis access—EHR, claims, labs, pharmacy and inbox—and how quickly does each source update?”

Design question

03

Reasoning triggers

“Should Praxis run on a schedule, react to clinical events, respond to clinician requests, or support all three?”

Design question

04

Autonomy boundaries

“Which actions may Praxis complete automatically, and which must remain drafts or recommendations for clinician approval?”

Design question

05

Approval and escalation

“Who may approve each action, how long should approval remain valid, and what happens when nobody responds?”

Design question

06

Success measures

“What outcomes define success, and what safety, latency and cost limits must the system satisfy?”

If answers are unavailable

State explicit assumptions, design the boundaries around them, and make those decisions easy to revise.