Integration that works in real hospitals
“Integration” sounds simple until you’re dealing with live clinical workflows, vendor constraints, and systems that were never designed to talk to each other.
JTX IT Consultancy delivers healthcare IT integration services across New Zealand, Australia and APAC with a pragmatic approach: design for safety, build for operability, test like go-live matters (because it does).
What we integrate
We commonly connect:
- PAS / EHR with lab (LIS), radiology (RIS/PACS), pharmacy, billing and downstream clinical apps
- National and regional services (e.g., patient demographics, identifiers, referrals, results distribution)
- Identity and access (SSO, directory services, role context, audit)
- Data platforms for analytics and reporting (secure extraction, events, APIs)
Core capabilities
End-to-end delivery, from discovery to steady state.
Design and standards
- Integration strategy and architecture: target patterns, governance, sequencing, standards
- API integration: REST/SOAP, gateways, OAuth/JWT patterns, throttling and observability
- Security by design: least privilege, secure transport, PHI handling and compliance alignment
Build, test, cutover, operate
- HL7 v2: ADT/ORM/ORU, acknowledgements, error handling, monitoring
- FHIR: server patterns, profiling, validation, subscriptions/events
- Testing and go-live: SIT/UAT support, regression, cutover planning, hypercare
- Operational readiness: dashboards, alerts, runbooks, handover and support models
Next step: a 20-minute fit check
Tell us what you are integrating, where the risk is, and what good looks like. We will outline the fastest safe path forward and be direct about where the real delivery pressure sits.
Contact JTX IT
Why clients choose JTX for integration work
We are usually engaged when the work carries delivery risk, executive visibility, or clinical sensitivity that requires stronger ownership than a generic integration build team can provide.
- Senior-led delivery with direct access to the people making design and implementation decisions
- Healthcare context across PAS, EMR, lab, radiology, identity, and national service integration
- Practical risk calls on what is ready, what is not, and where operational exposure still sits
- Delivery that survives go-live through testing, cutover planning, and operational readiness
HL7 v2 integration
HL7 v2 still underpins most hospital interoperability, which means reliability matters more than theory. We design and stabilise interfaces with acknowledgements, retries, queue behaviour, monitoring, and clear operational ownership so clinical data keeps moving when pressure is on.
- Common message flows: ADT, ORM/ORU, results distribution, scheduling and downstream clinical systems
- Reliability patterns: acknowledgements, replay, idempotency, dead-letter handling, alerting that reduces noise
- Interface specifications: message contracts, mapping logic, field-level decisions, error handling
FHIR integration
FHIR brings modern API-based interoperability to healthcare, but successful delivery still depends on the unglamorous details: profiles, terminology, validation, security constraints, and how the solution behaves under real clinical workflows rather than in a vendor demo.
FHIR delivery services
- FHIR readiness assessment: endpoints, resources, auth model, terminology, conformance expectations
- FHIR API delivery: resource mapping, profiles, validation, paging, error handling
- FHIR server patterns: when to use a FHIR server vs a translation layer
- Eventing: subscriptions and event-driven updates where appropriate
Security, compliance and operations
- OAuth/JWT patterns: scopes, client credentials vs delegated access, least privilege
- PHI handling: transport security, audit-friendly logging, environment separation
- Operational visibility: meaningful alerts, dashboards, and runbooks
- Testing and validation: conformance checks, regression testing, and safe cutover plans
HL7 v2 → FHIR transformation
Many hospitals operate hybrid estates: HL7 v2 internally, FHIR at the edges. We help organisations translate and normalise safely, with clear mapping decisions, validation, and operational ownership.
- Mapping approach: field-level decisions documented and versioned
- Validation: schema + profile validation, predictable error responses
- Change control: release windows, rollback plans, and stakeholder sign-off aligned to clinical reality
Platforms we work with
We’re platform-agnostic, and we’ll work with what your organisation has already standardised on.
Where it matters, we bring deep hands-on experience in healthcare integration engines and data platforms:
- InterSystems (Ensemble / IRIS for Health): complex routing, transformations, and high-throughput processing
- Rhapsody: healthcare interoperability delivery and operational support
- Mirth Connect: cost-effective HL7 integration patterns and channel governance
- Cloverleaf: high-availability interface estates and controlled change
- MuleSoft: API-led connectivity for enterprise integration programmes
How we deliver (so it doesn’t break later)
Most integration pain shows up after go-live: silent failures, alert fatigue, poor visibility, brittle mappings, and unclear ownership when something breaks at 2am.
Our delivery approach is designed to avoid that:
- Clear interface specifications (message contracts, mapping logic, field-level decisions, error handling)
- Operational visibility (dashboards, alerts that mean something, and audit-friendly logs)
- Change control that fits clinical reality (release windows, rollback plans, stakeholder sign-off)
- Security by design (least privilege, secure transport, PHI handling and compliance alignment)
Case example: Auckland District Hospital (2022–2024)
A major modernisation programme with a strong integration component, including:
- System replacement support: upgrading legacy patient management systems to TrakCare 2024
- Integration overhaul: modernising dozens of HL7 integrations to align with updated messaging frameworks
- Database integration transition: moving large volumes of database-style integrations toward standards-based patterns
- FHIR interoperability: early work integrating with national FHIR interfaces for demographics and identifiers
Note: details are summarised for confidentiality. We can walk through comparable delivery patterns, risk controls, and lessons learned during a fit-check call.
Common engagement types
- Integration uplift: stabilise an existing interface estate, improve monitoring, and reduce operational fragility
- New system onboarding: bring a vendor system into a hospital ecosystem with clear specifications, testing, and go-live control
- Interoperability programmes: define and deliver HL7/FHIR strategy, governance, and implementation across multiple vendors
- Project recovery: reduce go-live risk where interfaces are late, unclear, or failing in test and leadership needs a practical reset
FAQ
Yes. We build and support HL7 v2 interfaces (ADT/ORM/ORU and more) and FHIR-based integrations including FHIR server patterns, API integration, validation and operational monitoring.
Absolutely. We are platform-agnostic and regularly work with InterSystems, Rhapsody, Mirth, Cloverleaf and MuleSoft, as well as vendor-specific interface tooling.
Usually: the systems involved, message/API types, volumes, environments, interface count, required standards (HL7/FHIR), security constraints, and go-live timeframe. We can start with a short fit-check to confirm the approach.
Next step: a 20-minute fit check
Tell us what you are integrating, what is stuck, and where the delivery risk sits. We will propose clear next steps and a sensible path that matches operational reality, not wishful thinking.
Contact JTX IT