Product overview
Everything in OrderIntake
Five intake channels feed one work queue for staff, with a review pipeline, tenant-scoped APIs, and administration tools for receiving providers — plus compliance-oriented controls called out separately below.
Scan all capabilities in one table. Compliance rows are highlighted.
| Category | Feature | Description |
|---|---|---|
| Intake channels | Soft fax | Provision a dedicated fax number. Incoming images run through OCR and mapping on hosted models you do not bring keys for. |
| Intake channels | HL7 ORM & FHIR ServiceRequest | HTTPS endpoints for structured hospital feeds. Parsed fields merge with the same review and export pipeline as fax. |
| Intake channels | Online Order Site | Browser form for physicians and clinics at a tenant-branded URL. No staff login required for upstream submitters. |
| Intake channels | Inbound API | Tenant-scoped REST endpoint for EHR and portal integrations. Keys and URL are paired so orders cannot cross tenants. |
| Extract, map, and review | Work queue for staff | Inbound orders surface in a single tenant work queue your team works from — filter by status or channel, open the original artifact, and move items to ready. |
| Extract, map, and review | Hosted OCR and mapping | Unstructured fax and similar artifacts pass through extract and map steps. Structured HL7, FHIR, Online Order, and API payloads skip redundant model work. |
| Extract, map, and review | Review when it matters | Missing required fields or low-confidence extraction flag items in the staff work queue with the reason shown — not a silent guess. |
| Extract, map, and review | Required fields & confidence threshold | One tenant-wide field list and OCR/mapping threshold applies to every channel, including the public Online Order form and inbound API. |
| Extract, map, and review | Sending NPI guidance | Plain-language mapping hints per sending NPI improve model output. NPPES lookup on review surfaces public registry contact data. |
| Extract, map, and review | Pipeline view | Order detail shows the original artifact beside extraction, mapping output, and readiness — including which hints were in play at intake. |
| Downstream integration | Outbound API | Separate API keys for partners that pull orders already in your tenant. Filter by status, channel, and page through the same tenant URL. |
| Downstream integration | Export formats | Staff export CSV, JSON, or a FHIR Bundle from the orders list for billing, EHR, or analytics workflows. |
| Downstream integration | Integrator guide | Tenant admins download a PDF with sample requests, required fields, and health-check endpoints — without embedding secrets. |
| Tenant administration | Isolated tenant databases | Each care provider receives a dedicated Postgres database. Platform routing stores channel addresses, not clinical payloads. |
| Tenant administration | Domain-locked users | Staff emails must match the company domain. Tenant-admins invite reviewers and additional admins. |
| Tenant administration | White-label branding | Optional logo, display name, and accent color on the staff app, Online Order Site, and integrator materials — with OrderIntake attribution preserved. |
| Tenant administration | Usage billing | $3 per ingested order, counted through the month and invoiced when live billing is enabled. No tiers or monthly caps. |
| Compliance & governance | Encryption in transit and at rest | Clinical data and artifacts are protected throughout storage and delivery. Master routing tables do not hold PHI. |
| Compliance & governance | Per-tenant data isolation | Logical separation by dedicated tenant database supports access boundaries expected in HIPAA environments. |
| Compliance & governance | Role-based access | Super-admin, tenant-admin, and staff roles limit who can configure channels, users, keys, and clinical queues. |
| Compliance & governance | Enterprise SSO (OIDC) | Optional single sign-on through your identity provider. MFA stays with your directory when SSO is enabled. |
| Compliance & governance | Session and credential policy | Configurable idle timeout, password lifetime, and API key rotation planning with advance reminders — without automatic key revocation surprises. |
| Compliance & governance | Audit trails | Staff and API activity is logged with actor, action, and resource references. Audit entries carry metadata, not patient clinical content. |
| Compliance & governance | Accountability on removal | Orders and configuration items can be soft-removed from active use while retaining history for investigation and restore. |
| Compliance & governance | BAA-ready go-live | Execute a business associate agreement with OrderIntake before production PHI — not after the fact. |
Compliance rows are grouped under Compliance & governance. For security questionnaires and BAA discussions, contact us during evaluation — details are not published on this marketing site.