Clinical decision support software that shows clinicians why.

We build decision support tools: rule-based checks, reminders and AI assistants that cite their sources. The clinician sees the reason for each suggestion and makes the decision.

Doctor holding a phone with the app home screen and the day's route

What does clinical decision support development include?

Onix Health builds clinical decision support tools: rule-based checks your clinicians define, reminders and care pathways, and AI assistants that cite the source of each suggestion. They can open inside the EHR through SMART on FHIR or CDS Hooks. The clinician sees the reason for each suggestion and makes the decision, and we document the logic so your regulatory lead can decide whether FDA device rules apply.

What we build: clinical decision support

1

Rule-based checks

Rules your clinicians define, such as dose ranges or missing tests, shown at the right step.

2

AI assistants that cite sources

Suggestions drawn from your guidelines and records, each with a link to its source.

3

EHR-embedded apps

Apps that open inside the EHR using SMART on FHIR or CDS Hooks, built from the vendor's documentation and sandbox.

4

Reminders and care pathways

Step-by-step pathways per condition, with reminders when a step is overdue.

5

Alert tuning

Tracking of which alerts staff ignore, so rules that do not help can be changed or removed.

6

Testing against real cases

A set of real examples with known answers, run on every change to the rules or the model.

How the project runs

  1. 1

    Free technical audit

    Five working days. We look at your current system, data and plans, and you get a written report with what we found and what we would do.

  2. 2

    Define the rule or question

    We agree with your clinicians what the tool should check or suggest, and where in the workflow it appears. You get a dated plan.

  3. 3

    Check the regulatory path

    Your regulatory lead decides if the feature falls under FDA device rules. We document the logic so that decision is easy to make.

  4. 4

    Build, test, launch

    We test every rule against real examples, sign a BAA before patient data, and pass a penetration test before launch.

Technology and standards

  • SMART on FHIR
  • CDS Hooks
  • FHIR R4
  • Claude
  • AWS Bedrock
  • Python
  • Node.js
  • React
  • PostgreSQL
  • AWS
  • Built to the HIPAA Security Rule
  • Scoped against FDA clinical decision support guidance
  • BAA signed before any patient data is shared
  • AI answers cite their sources
  • Penetration test passed before launch

Questions about clinical decision support

1

What is clinical decision support software?

It is software that gives clinicians checks, reminders or suggestions while they care for a patient. Examples are dose-range checks, overdue test reminders and guideline lookups.

2

Is clinical decision support a medical device?

Sometimes. Under FDA guidance, software that lets a clinician see and check the basis for each suggestion is often not a device, while software that drives a diagnosis or treatment can be. Your regulatory lead makes the call, and we document the logic to support it.

3

Can decision support run inside our EHR?

Yes, through standards such as SMART on FHIR and CDS Hooks. We have shipped Epic and athenahealth integrations, and for new parts of any EHR we work from the vendor's documentation and sandbox.

4

Can you use AI for clinical decision support?

Yes, as an assistant that cites its sources and leaves the decision to the clinician. We run Claude through AWS Bedrock or Anthropic directly and test it against real examples before launch.

5

How do you keep alerts from being ignored?

We track which alerts staff override and review them with your clinicians. Rules that do not help get changed or removed.