Questions healthcare teams usually ask before getting started.

Small teams can start with a single documentation workflow once account setup, payment and any required agreements are complete. Integrations or more complex implementations may take longer.

Choose a plan, set up your organization, complete any required BAA or security steps, add your team, configure the first documentation workflow and start using TeddyIQ.

No. You can start with the documentation workflow causing the most work and expand from there.

Yes. Onboarding support depends on the plan and the complexity of the workflow. Grizzly includes priority onboarding.

No lengthy certification process is required. TeddyIQ is built around clear case status, exceptions and the actions your team needs to take.

Yes. You can try the Interactive Demo or book a live demo.

No. It takes the repetitive documentation work off your team, and brings them the cases that actually need a person.

Instead of manually checking every case, your staff can spend more time on exceptions, unresolved issues and decisions that actually require judgment.

Routine steps can move automatically when the evidence supports them. Uncertain, conflicting or unsafe situations go to a person instead of being guessed at.

Yes. TeddyIQ supports role-controlled access so people can reach the information and actions appropriate to their responsibilities.

Not always. Where supported, outside participants can use secure invitation and upload workflows without becoming full TeddyIQ users.

It works beside them. TeddyIQ does not replace your EHR and does not replace your billing or RCM software. A team can start using it alongside what it already runs, with one documentation workflow, and closer connections can be added later where the other system supports them.

No. Your EHR remains your clinical system of record. TeddyIQ focuses on documentation work and exceptions that happen between systems, organizations and people.

No. TeddyIQ complements those systems by helping verify the documentation their workflows depend on.

No. TeddyIQ works around the systems you already use, and connects to them where that is supported.

TeddyIQ does not currently advertise a broad public API. API access and integrations depend on the workflow, plan and systems involved.

Integration options depend on the platform, workflow and technical access available. We confirm what is currently supported during implementation review.

The workflow can still support outside participation through available secure request, invitation and upload methods.

TeddyIQ supports protected healthcare workflows only once the account setup, safeguards and agreements are in place.

Yes. TeddyCare Medical provides a Business Associate Agreement for covered healthcare customers where appropriate.

TeddyIQ is built to support HIPAA-regulated healthcare workflows through safeguards including controlled access, encryption, secure upload handling and audit history. TeddyCare Medical provides a BAA where appropriate.

Uploads are quarantined while required safety checks run. Files are released into the workflow only after the required checks pass. Files that cannot be safely cleared remain blocked.

Yes. TeddyIQ protects supported healthcare data in transit and at rest.

Access depends on authenticated identity, organization membership, assigned responsibilities and role permissions.

Yes. TeddyIQ maintains an append-only audit history for supported application events.

It stops and brings the exception to a person instead of guessing.

TeddyCare Medical does not claim certifications it has not earned. Current security controls and certification status are available during security review and on the Security page.

Cub is for solo professionals and very small operations. Kodiak is for small teams. Grizzly is for growing organizations. Larger or more complex organizations can request custom pricing.

One case is one defined documentation workflow for one subject and one purpose, from request through verified completion. Multiple requests, resends, corrections, follow-ups and missing-document retrievals inside that workflow are activity within the same case, not separate cases.

No. Sending a second request, resending to the same office, correcting a date range or retrieving a document that never arrived are all activity inside the case that needed them. You are never charged more because a workflow took more attempts.

We talk to you about it. Consistent usage above your plan is handled by moving to a larger plan or a custom volume agreement. Standard plans do not use surprise overage charges, and the requests inside a case are never billed separately from it.

There is no standard onboarding fee for Cub, Kodiak or Grizzly. Custom integrations or unusually complex implementation work may be quoted separately.

Business subscriptions are paid securely through Stripe.

Yes. Monthly billing is available. Save 10% with annual billing.

Yes. You can move to a plan that better matches your users and case volume as your organization grows.

No separate patient subscription is required for invited participation in a business workflow.

TeddyIQ can check whether expected documentation arrived, whether required evidence is present, whether the documentation matches the case, whether dates and requirements line up, whether permission requirements are satisfied and whether something still needs resolution.

No. Retrieval can be part of the workflow, but TeddyIQ focuses on verification and exception resolution. Moving a file is not the same as confirming that the documentation is actually ready.

No. TeddyIQ is workflow software for healthcare documentation. It checks what arrived, flags what is missing or wrong and sends uncertain cases to a person.

Yes. AI can make mistakes. That is why TeddyIQ is built around verification, defined checks and human review when the evidence is not clear enough.

Open the Verification Receipt on the case. It lists what was checked, what passed, which checks a person settled rather than the system, and how each document reached TeddyIQ. If something a check relied on changes afterwards, the case says so instead of keeping a receipt that is no longer true.

Yes. Requirement-level verification, Verified Complete and the Verification Receipt are included on Cub, Kodiak and Grizzly. Plans differ by how many people and cases they cover, and by the team and service features that come with a larger operation.

TeddyIQ surfaces the problem, determines whether a routine fix can safely move forward and either continues the correction or sends the exception to a person. The case is completed only after the required checks pass.

Product direction. TeddyIQ’s product direction includes using successful resolutions as reusable repair patterns so repeated failures can require less unnecessary rework and human intervention over time. This is not running against live cases today.

Yes. Try the Interactive Demo or book a live demo.