Challenge
A copied action list keeps an old routing rule, so a new system receives messages meant for another.
Agnotic approach
Every new action list starts from a reviewed template, and routing rules are tested with messages for each receiver.
Integrations / Corepoint
Corepoint Integration Engine Services
A new lab system needs feeds by go-live, the engine is two versions behind, and nobody has tested failover since it was installed. Agnotic Technologies builds and changes interfaces on your existing Corepoint Integration Engine, now part of Rhapsody's portfolio, and leaves every change documented for your team.
ConnectionsAction listsUpgradesFailover checks
Trusted by global innovators
Corepoint work
What do Corepoint integration engine services cover?
Corepoint integration engine services are the build, change and support work on an existing Corepoint Integration Engine: new inbound and outbound connections, action list and message model changes for a new EHR or lab, version upgrades, high availability checks and documentation. Agnotic Technologies does this work inside your Corepoint environment, alongside your interface analysts.
Corepoint is built for analysts to configure without code, so many estates grow quickly and unevenly. Our job is usually to add capacity for a backlog, make older configuration understandable and keep the engine on a supported version.
If your organization has already chosen another engine, our interface engine migration page covers that move instead.
Concepts to work
How do Corepoint's building blocks map to interface work?
Most change requests touch one or two of these. Naming the right one up front keeps a small change small and tells us what to test.
| Corepoint concept | What it holds | Typical change request | What we test before promotion |
|---|---|---|---|
| Connections | The inbound and outbound links to each system, with protocol, address and acknowledgment settings | A new lab, a moved EHR server or a new certificate | Connectivity, acknowledgments and behavior when the other side is down |
| Action lists | The steps that run on each message: filtering, mapping, routing and error handling | A new receiving system or a changed routing rule | Captured messages run through the changed action list, with output compared field by field |
| Message models | The definition of each partner's message structure, including local segments and fields | A new EHR or lab version that changes its message layout | Parsing of real sample messages and rejection of malformed ones |
| Validation and error handling | The rules for what happens when a message is incomplete or cannot be delivered | Missing patient identifiers or codes the receiver does not accept | Each failure path, so nothing is dropped without an alert |
| Monitoring and alerts | Queue, connection and error alerts, and who receives them | A feed that went quiet without anyone noticing | Alerts for errors and for silence, sent to the people on call |
Names and screens differ between Corepoint versions. We work from the version you run and your own configuration, not from a generic template.
Corepoint work hospital teams bring to us
Scoped one change at a time, or as a backlog worked through with your interface team.
New feeds
Inbound and outbound connections and action lists for a new lab, radiology, pharmacy, device or payer system.
Changes for a new EHR or lab
Message models and mappings updated when a sending or receiving system is replaced or upgraded.
Version upgrades
Moving the engine to a supported Corepoint release, with output compared before and after.
High availability and recovery checks
Failover and restore tests on estates that run the high availability or disaster recovery options.
FHIR, X12 and database connections
REST and FHIR endpoints, X12 files to clearinghouses and SQL reads or writes alongside HL7 v2 feeds.
Estate documentation
A written inventory of every connection and action list, with purpose, owner and test messages.
Failure points
Where do Corepoint estates break?
The problems we find most often when we first review an estate, and how we fix each one.
Challenge
A message model was edited for one sender and now rejects valid messages from another.
Agnotic approach
Each partner gets its own model where structures differ, and model changes are run against sample messages from every sender that uses it.
Challenge
A certificate on an outbound connection expires and the feed stops overnight.
Agnotic approach
Certificate expiry dates are listed per connection and alerted well before they lapse.
Challenge
Alerts fire on errors but not when a busy feed goes quiet.
Agnotic approach
Each important feed gets an expected message rate and an alert when it falls silent during working hours.
Challenge
Failover was configured at install and never tested since.
Agnotic approach
A planned failover and restore test, with a written result, before and after every upgrade.
Challenge
Test and production configurations have drifted apart.
Agnotic approach
Changes are promoted in one direction with a record of what moved, and test is refreshed from production before large changes.
New feed
How do we take a new feed live on Corepoint?
The same steps for every new interface, so go-live is predictable.
Agree the specification
Message types, trigger events, fields, code sets and acknowledgment rules agreed with both system owners.
Collect sample messages
Real samples from the sender's test system, with patient data replaced by test patients.
Build the connection and action list
Model, mapping, routing and error handling built in your test environment.
Test with both sides
Messages run end to end and checked by the receiving team, including the failure cases.
Promote and watch
Moved to production in an agreed window, with message counts watched closely in the first days.
Failover
What does a high availability check cover?
Estates that run Corepoint's high availability or disaster recovery options still need proof that failover works. We check the following.
- Which servers, databases and network paths the failover depends on, written down in one place
- Whether queued messages survive a failover without loss or duplication
- How sending systems reconnect, and whether any need a manual restart
- How long a restore from backup takes, measured in a test rather than estimated
- Who is alerted during a failover, and whether the runbook matches what actually happens
- Results recorded as evidence for the contingency plan your security team keeps
Around the engine
Which systems sit around a Corepoint engine?
The systems we connect most often through Corepoint, by standard.
HL7 v2 feeds
- EHR admissions, orders and results
- Lab, radiology and pharmacy systems
- Scheduling and billing systems
FHIR and REST
- Patient-facing and partner apps
- Cloud services and APIs
- FHIR servers and registries
X12 and files
- Clearinghouses and payers
- Batch file drops and SFTP
- Document and image archives
Databases and queues
- SQL reads and writes
- Message queues such as AMQP brokers
- Reporting and data warehouse loads
Compliance-First Healthcare App Development Services Backed by Global Standards
01
HIPAA
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, strict access controls, and traceable audit logs.
02
GDPR
General Data Protection Regulation
Implement lawful consent flows, data minimization, retention controls, and secure processing for sensitive health data.
03
FHIR
Fast Healthcare Interoperability Resources
Enable standardized health data exchange across apps, care teams, and systems through standards-based FHIR APIs.
04
HL7
Health Level Seven International
Support enterprise-grade interoperability with HL7-based integrations for records, events, and clinical messaging workflows.
05
HITRUST
Health Information Trust Alliance
Align security programs to healthcare-specific control and risk management practices trusted by providers and ecosystem partners.
06
HITECH
Health Information Technology for Economic and Clinical Health Act
Design with breach notification readiness, digital record safeguards, and operational controls that support regulated care programs.
07
SaMD
FDA Software as a Medical Device
Plan software quality, traceability, and documentation pathways for products that may require SaMD review and submission.
08
MDR (EU)
Medical Device Regulation (European Union)
Prepare EU market-ready processes for risk classification, evidence tracking, and lifecycle governance under MDR expectations.
09
SAMHSA
Substance Abuse and Mental Health Services Administration
Apply confidentiality controls and consent-aware sharing models for behavioral and mental health data experiences.
Scope and cost
What drives the cost of Corepoint work?
We do not publish prices. These factors set the scope, which we confirm on the scoping call.
Number of connections
How many feeds a change touches, and how many receiving teams must test and sign off.
Undocumented configuration
How many action lists and models need reading and documenting before they can be changed safely.
Version gap
How far the running version is from a supported release.
Environment parity
Whether the test environment matches production closely enough to trust its results.
Failover setup
Whether the estate runs high availability or disaster recovery options that need testing.
Who it is for
Teams that use our Corepoint services
Teams that run Corepoint today and want more capacity or more certainty.
Hospital interface teams
A backlog of new feeds and changes, and too few analysts to clear it.
Labs and imaging groups
Order and result interfaces with many referring practices and EHRs.
Teams replacing an EHR or lab system
Models and action lists updated without disturbing unrelated feeds.
IT leaders planning an upgrade
A supported version reached with evidence that every feed still works.
Teams that lost a key analyst
Configuration that only one person understood, now documented.
How we work
From scoping call to hand-over
Three stages, starting with the estate as it is today.
1.
Scoping call
We hear about your Corepoint version, environments and the most urgent change.
Backlog2.
Estate review
An inventory of connections and action lists, a check of alerts and failover, and a ranked list of risks.
Fixed scope3.
Build, upgrade and hand over
New feeds, changes or an upgrade, then documentation and pairing sessions with your analysts.
OngoingFacts and sources
Which facts shape Corepoint work?
Short facts the work is designed around, each linked to its primary source.
Rhapsody describes Corepoint as supporting FHIR, HL7, REST, CDA, X12/EDI, SQL and AMQP interfaces, and says it can be deployed as SaaS, on the customer's own infrastructure or as an Integration Platform as a Service (iPaaS).
Source: Rhapsody, Corepoint Integration Engine product pageRhapsody lists high-availability and disaster recovery add-ons for Corepoint, described as helping organizations keep running whatever the challenge.
Source: Rhapsody, Corepoint product brochureHL7 calls its Version 2 messaging standard the workhorse of electronic data exchange in the clinical domain, and notes it was first released in October 1987 as an application protocol for electronic data exchange in healthcare environments.
Source: HL7 International, HL7 Version 2 Product SuiteThe HIPAA Security Rule requires a contingency plan for responding to an emergency or other occurrence, such as system failure, that damages systems containing ePHI, including a disaster recovery plan with procedures to restore any loss of data.
Source: 45 CFR 164.308(a)(7) (eCFR)The HIPAA Security Rule requires policies and procedures to protect electronic protected health information from improper alteration or destruction.
Source: 45 CFR 164.312(c)(1) (eCFR)
Frequently Asked Questions
Yes. We work in your test environment through your change process, and changes reach production the way your team already promotes them. We do not install a second engine to do the work.
Yes. We read each action list, write down what it does and which systems depend on it, and build a set of test messages that proves its behavior before anything is changed.
Captured messages, with patient details replaced by test patients, are run through the changed connection or action list in test, and the output is compared with the expected result for the receiving system. The receiving team signs off before promotion.
If the engine works, your analysts know it and the licence suits you, upgrading is usually the smaller job. A move makes sense when your organization has chosen another platform for other reasons. Our estate review gives you the inventory either way.
The number of connections a change touches, how much undocumented configuration sits behind them, the version gap, whether test matches production and whether failover needs testing. We size each change or backlog on the scoping call.
This page makes no partner claim. Agnotic Technologies is a software development services company that works on the Corepoint licence you already hold. Licences, product support and new versions come from Rhapsody.
An engineer may use AI tools to summarize an exported configuration or draft synthetic test messages. A person reviews every change, and production messages containing PHI stay inside your environment.