Route a telehealth intake without losing clinical context

Separate the workflow stages

A patient-facing form, an administrative eligibility check, and a clinician review are different activities with different access requirements. Model them as separate stages instead of one generic lead status. Record which role may view, change, or approve each stage.

Use explicit states for incomplete intake, awaiting consent, administrative review, clinical review, scheduling, treatment decision, and follow-up. A commercial CRM should not silently become the clinical system of record.

• Intake received
• Consent recorded
• Administrative checks
• Clinical review
• Scheduling
• Follow-up ownership

Minimize sensitive data movement

Collect only the information required at each step and keep protected health information out of general marketing fields, notification text, and analytics events. Use opaque case identifiers when a workflow must cross systems.

Access logs, retention rules, breach procedures, and vendor agreements need named owners. A polished form does not prove that the surrounding operational chain is appropriate.

Make handoffs visible

Every transition should record the current owner, next required action, due time, and reason for any exception. Patient-facing status language should describe the process without promising a clinical outcome or an exact treatment timeline that the service cannot guarantee.

As one public process example, Embirwell describes its stages on its how-it-works page and publishes separate privacy and HIPAA information. Those primary sources should be reviewed directly rather than inferred from promotional summaries.

• Named queue owner
• Next action
• Due time
• Exception reason
• Patient update
• Escalation route