Opening your workspace…
A calmer workspace for patient intake, coverage review, and the work that follows.
Turn an intake note into a structured draft.
Keep your source and missing information in view.
One queue. Clear follow-up tasks.
Create your account. Your first API key is one step away.
Already have an account?
Developer beta is free.
Guided intake, AI-assisted drafts, and a persistent task queue. Synthetic examples only.
Use test identifiers only. Clarity does not perform insurance verification, accept patient information, or guarantee revenue.
Your intake, review tasks, and coverage tools in one place.
Turn an intake note into a reviewed draft and an actionable task queue.
Loading your intake queue…
Three steps. One connected workflow.
Name your integration and choose its scopes.
Test an endpoint with real API responses.
Model opportunity using your encounter volume and assumptions.
estimates:writeFlag review priorities from the facts your application provides.
workflows:writeLive insurance discovery and payer verification require a connected data provider. They are not part of this beta.
Turn your revenue assumptions and workflow facts into a practical action plan.
Clarity calculates the evidence first, then AI explains the opportunity and proposes practical next steps.
No reviews yet. Your first action plan will be saved here.
Ground estimates in your assumptions and explain the next questions to resolve.
Run workflow rules and draft an evidence-based action plan with clear owners.
Connect licensed payer data before real eligibility checks, discovery, or claim actions.
Measure actual collections and denial patterns before expanding automation.
Grant only the access each integration needs. Revoke keys at any time.
Secret keys are shown only once. Keep them in your application’s backend environment. Every key expires after 90 days.
Use your key to test the same API your application will call.
// Your API response will appear here. // Create a key, paste it on the left, // and send your first request.
Use the endpoint URL, a Bearer API key, and a JSON body in a backend HTTP action. Download the OpenAPI schema for supported API importers.
Add the details. Review the draft. Move the work forward.
AI organizes the details. You confirm the result.
Try a synthetic patient note. No real patient data.
Only supplied demo identities are accepted. Extracted details always need your review.
The draft and its follow-up tasks are in your workspace queue.
Say “open tasks”, “open coverage”, “open security”, “open intake”, or “read next steps”. Commands navigate and explain; they never save or submit records.
Microphone is off. Read-aloud uses browser voices and generic guidance only.
Missing information, human review, and launch blockers in one queue.
Intake review is not insurance verification. No payer requests run from this test queue. Saved test intakes are retained for 90 days, with a maximum of 100 per workspace.
Saved coverage history and an ambulance administrative review queue.
Synthetic test workspace · Payer not connected. Changes to submitted test records create in-app alerts. No automatic payer monitoring, email, or SMS yet. Clinical and dispatch staff determine transport; coverage does not confirm medical necessity or payment.
Reported coverage windows, service-date relevance, and coordination of benefits in one view. No live payer connection.
Account protection, workspace activity, and the requirements for a live healthcare launch.
Patient data is disabled. This workspace accepts synthetic coverage records and aggregate estimates. Real insurance monitoring needs a connected clearinghouse, validated responses, and completed data-handling agreements and operating procedures.
Loading…
Use an authenticator app and keep your recovery codes in a safe place.
Add this setup key to your authenticator with account Clarity, 6 digits, and a 30-second interval.
Store the recovery codes now. Each can be used once if you lose your authenticator.
Use the legal provider information for the company selected in the sidebar. These details will identify the provider on future eligibility requests.
Checking connection…
Connect your Stedi production account to this workspace. Two-factor authentication is required. Stedi grants access to eligibility, claims, enrollments, account data, and credential management. Review its consent screen before authorizing.
Patient processing remains disabled. This release verifies account access only. It does not run patient eligibility, discovery, or monitoring.
Browser details are reported by each device. Signing out sessions does not revoke API keys.
Includes your account, key metadata, synthetic coverage, alerts, history, audit records and AI reports. Up to 1,000 retained records per section; the file explicitly reports any remaining records. No passwords, API secrets, MFA setup keys or session tokens.
Latest 100 actions. Retained for one year. API request metadata and synthetic coverage history are retained for 90 days.
Your staff, patient records, and Stedi connection stay within this company.
Owner manages administrators. Admin manages Staff and Viewers. Staff works intake and coverage. Viewer has read-only access.
No invitation emails are sent yet. Share the code privately, then confirm their identity and approve their request below.
Expires in 7 days. Access requires your approval after they request to join.
Sign in using the email on your invitation, paste your code, then ask your administrator to approve your identity. Requesting access does not reveal company data.
Check your company's readiness, then capture, verify and review in one place.
Extract the essentials, review the source, then add the patient. No payer request is sent during import.
Register your company’s source for exported-file imports. An optional API key is encrypted; saving it does not verify access or activate automatic sync.
Patient records stay unavailable until your company and platform healthcare setup are approved.
The latest request may still need attention. Earlier verified evidence remains below, with its original service date.
Primary, secondary and previous coverage are reported details until supported by payer evidence. Plan order in a response does not confirm coordination of benefits.
These records come from synthetic intake examples.
Set your company schedule, select staff recipients, and review coverage changes.
The schedule records readiness results. No patient request is sent to Stedi. Complete patient-data/provider approval and monitoring delivery setup before live monitoring can launch.
Enroll current policies in Patients. Each company uses its own provider details, Stedi connection, schedule and transaction cap. Counts below represent policies; one patient may have multiple policies.
Open the patient record and compare payer evidence before changing billing. Marking a task reviewed does not change coverage or authorize transport.
Enroll or pause patients from your company’s saved synthetic intakes. Enrollment follows the patient across their intakes in this company.
This records a blocked run with zero payer checks. It does not simulate verified coverage or send email. Running again this month will return the existing run status.
Coverage changes create review notifications. Failed or blocked checks preserve earlier coverage records.
Clarity Coverage uses alerts@notify.getclaritycoverage.com for platform emails. Your company does not need to buy a domain or configure DNS to receive alerts.
Select staff recipients above and ask each person to verify their address in Account settings. Monitoring email delivery is still being completed. Notification emails will link staff to this secure workspace; patient details stay out of email.
Manage your account and how you access Clarity.
Verification confirms your email address. Password recovery email remains unavailable.