For IT and integration stakeholders
ClinChek IT & Integration Guide
Evaluate data access, responsibilities and connection scope without replacing your existing hospital systems.
Readiness depends on recorded requirements, inventory and the last update. Stale stock data can incorrectly show a procedure as ready. Your team must verify current physical stock; ClinChek does not replace clinical checks.
Interoperability, with clear boundaries
Your systems. A scoped connection.
CSV imports and the organization-scoped ClinChek API are available today. Epic, Cerner, Oracle, Workday and Infor connections require evaluation and custom implementation; they are not live, certified or out-of-the-box ClinChek connectors.
Available now: ClinChek API
Read procedures, readiness, inventory, supplies, vendors, issues and supply requests. Create issues and supply requests. Administrators manage revocable API keys scoped to their organization.
Not automatic synchronization
The connection registry tracks administrator-entered details and status. A “Connected” label alone is not proof of a working vendor data feed. Vendor authorization, mapping, testing and monitoring are separate implementation work.
Start manually. Evaluate connections around your workflow—not the other way around.
Discuss your integration needs