Skip to content

Integrations

Fits into the systems you already run.

A full API, read and write. Your project data flows into your own dashboards, and data from your other systems flows in, so nobody retypes anything.

the same data your teams see

What teams connect it to

Out to your dashboards. In from your systems. Back where people look.

Three directions, one set of rules.

  • Out · your dashboards

    Improvement in your own reporting

    Put projects, audit compliance, PSIRF priority progress and savings beside your other performance data, in the BI tools your organisation already uses.

  • In · your other systems

    Data in, without retyping

    Send incidents themes in every night instead of a monthly spreadsheet. Bring audit measures in from your electronic patient record as monthly counts, never patient details. Keep departments and people in step.

  • Back · your incident reporting system

    Progress where people already look

    Your incident reporting system, or your own reporting, fetches each project's progress by its reference. Safety actions stay up to date without anyone pasting updates.

Your electronic patient record

Your EPR's numbers, straight into your audits.

Most audit measures already live in your electronic patient record. Your reporting team sends the monthly counts straight into your audits, so the charts update themselves and nobody retypes a number.

  • Counts per month, never patient details. They're checked on the way in like everything else.
  • Works with Epic and other EPRs, through your trust's own reporting.
  • Ready-made recipes for common measures, so your analyst sets one up in an afternoon.
  • Sepsis antibiotics within 1 hour
  • Falls per 1,000 bed days
  • Hospital-acquired pressure ulcers
  • VTE risk assessment

Review:Recipes are on the roadmap (integration API phase). Confirm before launch.

the monthly retyping, gone

The monthly copy-and-paste day

Nobody trained for years to copy cells between spreadsheets.

Most of the reporting work in improvement isn't analysis. It's moving numbers from one system to another.

Now

  • Export the incidents.
  • Tidy the spreadsheet. Upload it.
  • Copy the audit results into the board report.
  • Copy the progress into the safety action.
  • Repeat next month.

Connected

Themes arrive overnight. PSIRF priorities are always up to date.

Results appear in your dashboards. Improvement sits beside every other measure your board sees.

Progress updates itself in the systems people already check.

the copy-and-paste day disappears

Safe by default

The same protections as the app.

Writing through the API is held to the same rules as typing into Prep Medics. Your IG team doesn't need a second set of answers.

  • Patient details still blocked

    Everything sent in is checked for NHS numbers and other identifiers, exactly as when someone types.

  • Access you control

    Choose exactly what each key can read and what it can change, down to the kind of data. Turn a key off at any time.

  • Every call accounted for

    Every API call appears in your access log next to staff activity, so you can see what each integration read or changed.

  • Stored in London

    Data sent through the API is stored in London, like everything else in Prep Medics.

Tell us what you'd like to connect.

dashboards, incident systems, staff lists: tell us what you run