01
Incomplete intake
Required information is identified early, while there is still time to collect it.
Pre-visit decision infrastructure
Decide before the visit.
Dicyd sits upstream of scheduling, EHR, and billing systems to determine whether an appointment is revenue-ready before staff time and care are committed.
Deterministic decisionsVersioned location rulesAuditable transitions
Appointment readinessREADY
✓Intake completeverified
✓Payer acceptedlocation rule
✓Referral requirementnot required
✓Authorization readinessready
decision: revenue_ready
rule_set_version: location-12.v4
actor: decision_engine
result: same input → same output
rule_set_version: location-12.v4
actor: decision_engine
result: same input → same output
The operational gap
Revenue risk starts before an appointment reaches the schedule.
Dicyd checks the non-clinical prerequisites that determine whether staff should proceed, review, or intervene.
02
Coverage uncertainty
Payer acceptance, referral requirements, and authorization readiness are evaluated against explicit location rules.
03
Hidden exceptions
Cases that cannot proceed deterministically become visible staff tasks instead of silent failures.
How Dicyd works
A decision flow built for accountability.
Inbound information becomes a clear case state, a reason, and the next operational action.
1
Collect
Web intake captures only the information needed for revenue readiness.
2
Evaluate
Pure, versioned rules evaluate completeness, payer, referral, and authorization readiness.
3
Decide
The case moves to a deterministic state with a consistent reason code.
4
Act
Ready cases proceed. Exceptions enter a staff task queue for review and follow-up.
One pre-visit layer
Built to sit in front of the systems clinics already use.
Dicyd does not replace scheduling, EHR, or billing. It determines whether the appointment is ready to move into those systems.
Deliberately non-clinical: Dicyd does not provide medical advice, diagnosis, clinical triage, or clinical workflows.
Intake completenessValidate required fields and request missing information.
Payer and plan rulesClassify accepted, review, or not accepted using explicit location configuration.
Referral and authorization readinessEnforce administrative requirements before the visit.
Case state and decision historyRecord every transition, trigger, reason, rule version, actor, and timestamp.
Human exception queueRoute payer, authorization, confirmation, and callback work to staff.
Operational outcomes
Prevent unpaid work without creating another opaque workflow.
Decide earlierFind administrative blockers before the appointment consumes scarce staff and provider capacity.
Make exceptions visibleGive staff a focused queue with clear reasons and next actions.
Explain every resultUse deterministic rules and an immutable decision trail for operational review.
See Dicyd on your pre-visit workflow.
Start with one location, explicit rules, and a measurable 90-day pilot.