Custom Axiom nCare integration development
Axiom nCare is the medication solution from CareConnections of Leusden, part of the Axiom care platform. Care organisations use it to manage the medication process, from electronic prescribing to digital administration recording. CareConnections offers integrations with pharmacies, EHRs and medication packagers, and an API for administration data. If you want that data in your data warehouse, quality reporting or your own application, you need more than a standalone export. Appfront builds the integration between Axiom nCare and your systems, with only the data that is permitted and necessary.
What is an Axiom nCare integration?
An Axiom nCare integration connects CareConnections' medication solution to the systems around it. With Axiom nCare, a care organisation manages the medication process: the practitioner prescribes digitally (EPS), the care worker records the administration digitally (EMAR), with dosage checks and a four-eyes check. Medication is ordered from the pharmacy in a few clicks, lab results arrive via Axiom Connect, and staff work with the Axiom app, which has replaced the earlier nCare app. The integration puts the data you need into your own systems.
CareConnections itself offers integrations with EHRs, pharmacy information systems, medication packagers and quality management systems for incident reports (MIC and MIM), plus an existing Nedap integration for importing client and user data. There is also the CareConnections API. According to CareConnections, at this stage it focuses on administration data, via a FHIR endpoint for MedicationAdministration, and is updated once a day for the time being. CareConnections names BI tools such as Power BI, Qlik and Tableau as the destination. What has to sit in between is the actual work: retrieving the data, checking it, linking it to locations and departments, and putting it into the structure your reporting expects.
We build custom because every care organisation has different needs. Whether you want to see how often administrations deviate from the schedule per department, set medication alongside incidents or care intensity, or store administrations in your own data warehouse, that determines how the integration works. You request the API through Service Management in the CareConnections customer portal, and you receive your own client ID and secret. The API does not retrieve administrations incrementally and is unavailable at peak times; the integration takes this into account.
Administrations
From nCare into your overview.
Only what is permitted
With legal basis and permissions.
Alongside the record
Medication alongside everything else.
How we build your Axiom nCare integration
We start with your question: which medication data you need, for which locations, on what legal basis, and where it needs to end up. You then request the API from CareConnections and we build the first integration, usually the administration records into your data warehouse or BI environment, with an initial overview for a few departments. Once the figures match what is in nCare, the other locations follow, along with the integration with other data. After that, we maintain the integration whenever CareConnections extends the API or your systems change.
Data, locations, legal basis.
Administrations into your environment.
More locations and data.
Go-live, monitoring, and maintenance when things change.
What an Axiom nCare integration actually does
The components below appear in almost every Axiom nCare integration. Which ones you need depends on your question and on the systems you use alongside it.
Administrations
Retrieved via the FHIR API.
Locations
Organised by department.
Validation
Deviations flagged.
Selection
Only the data that is needed.
Access
Own client ID and permissions.
Reporting
To your BI environment.
Who we build an Axiom nCare integration for
The integration is intended for care organisations that work with Axiom nCare and want to use medication data outside nCare. The more locations and clients on medication, the more it delivers.
Elderly care
Multiple locations in view.
Disability care
Medication per home.
Mental health and youth care
Administrations alongside care.
Quality and BI
Figures for the organisation.
Technology and integrations
This page is about Axiom nCare from CareConnections. For exchanging medication data between care providers according to the national standard, see our page on the medication transfer integration; for the EHR, see our pages on the Nedap integration and the Caress integration. You can read about our approach on custom software development.
Why choose Appfront for your Axiom nCare integration?
A quality report compiled by hand from separate overviews, a department that doesn't see that administrations are often skipped, or medication data shared without it being clear why: all of this costs a care organisation time and trust. That is what we build around: only data that is permitted and necessary, checked against nCare, and an integration that shows when something went wrong.
Only what is permitted
Legal basis recorded up front.
Reviewed
Checked against nCare.
Visible
Errors in the log.
Security and privacy in an Axiom nCare integration
The integration processes clients' medical data, which falls under the strictest GDPR rules. It only uses data for which there is a legal basis and that is necessary for the purpose, works with the client ID and secret that CareConnections creates for your organisation, and logs every exchange with time and outcome.
The integration runs in a European data centre, with encrypted connections and storage. Keys are kept secure and are not visible to staff. We agree with you in advance who in your organisation may see which medication data, and where possible we report without data that can be traced back to the client.
Frequently asked questions about an Axiom nCare integration
Questions that care organisations, application managers and BI teams ask before they get started.
The medication solution from CareConnections in Leusden, part of the Axiom care platform. Care organisations use it to manage the medication process, from electronic prescribing to digital administration records, including ordering from the pharmacy and dosage checks.
The web environment is now called Axiom nCare and its content has remained the same. The earlier nCare app has been replaced by the Axiom app. For smaller organisations there is Axiom nCare Direct, a quick online implementation of administration recording.
Yes. At this stage, the CareConnections API exposes administration data through a FHIR endpoint for MedicationAdministration, with its own client ID and secret per organisation. You request the API through Service Management in the CareConnections customer portal.
Through the API you can retrieve medication administrations, including the time, the scheduled and administered dose, the double check and the location or department. For now, the data is updated once a day. For other data, we look at the integrations CareConnections offers.
According to its own website, CareConnections integrates with EHRs, and there is a Nedap integration for importing client and user data. A custom integration covers what falls outside that, such as medication data in your own data warehouse or alongside data from other systems.
The integration retries outside the periods when the API is unavailable, and puts an exchange that keeps failing in an error list with the reason attached. That way you can see which day or department is missing, and it is retrieved later.
For care organisations with multiple locations and many clients on medication, with their own data warehouse or BI team, or with quality questions that combine medication with other data. If the overview in nCare itself is enough, an integration is usually not needed.
Medication data from Axiom nCare in your own overview?
Tell us which medication data you need and where it should end up. We will show you how an integration handles that securely.