For digital, architecture and IG teams

Technology & Integration

PA-IQ sits alongside the systems you already run and turns what they hold into operational views. Here is how it fits, what it connects to, and where the data stays.

Where PA-IQ fits

PA-IQ sits alongside your existing clinical and operational systems. It reads what they already hold and turns it into operational applications and, when you connect them, one wider operational picture. It does not replace the EPR, the PAS or any other system of record.

Start with the problem. Work with the systems you already have.

The questions digital, IT and operational teams ask first, answered plainly.

How much work will our IT team need to do?

Less than a replacement programme. PA-IQ reads from the systems you already run, through the interfaces your estate already provides: HL7, FHIR and REST APIs, event feeds or structured extracts. Your IT team’s main involvement is agreeing what information is needed and how it is accessed, then providing that access.

What information do you need access to?

Only what the application you start with needs. Before anything is connected we agree, item by item, which information will be shown and which system it comes from.

Does PA-IQ replace or interfere with our EPR?

No. Your EPR, PAS and other source systems stay the systems of record. PA-IQ reads from them. Write-back is never assumed; any two-way integration is agreed explicitly.

How long does implementation take?

Typically live within 12 weeks of data access being agreed. The time before that depends on how quickly access can be agreed on your side.

What involvement is needed from clinical and operational teams?

They shape it. The first working version is built around your standard operating procedures on illustrative data, so your teams can see it and change it before anything is connected.

Systems PA-IQ works alongside

  • EPR and PAS — beds, admissions and discharges
  • ePMA — discharge medicines
  • Remote monitoring — virtual ward caseloads
  • Community and social care — referrals and packages

How data reaches PA-IQ

Depending on the source system, PA-IQ can take data through established healthcare integration methods: HL7 messaging, FHIR and other REST APIs, event feeds and structured extracts. Wherever practical we use the interface your estate already provides, and work alongside your existing integration engine rather than replacing it.

Before anything is connected, we agree with your IT and information teams exactly which information each application needs and where it comes from. Every item shown in PA-IQ is traced to its source, so what the application displays is transparent and agreed in advance.

Not every deployment uses every method. The route for each source is agreed with your IT team during implementation, and deployments are typically live within 12 weeks of data access being agreed.

Where the data is processed and held

PA-IQ runs inside your own environment. Patient data is processed and held on your network and stays there. Our team supports the system remotely, through access routes you approve and control.

Your systems stay the record

Your EPR, PAS and other source systems remain the systems of record. PA-IQ takes data from them and, where an application needs it, captures operational information within PA-IQ itself.

Write-back to a source system is never assumed. Any two-way integration is agreed explicitly as part of the deployment, so responsibility for the clinical record stays exactly where it is today.