Opening AdaptixCore
Opening the page you asked for.
Proof // Product evidence
No logos. No case studies. Every claim with its receipt.
AdaptixCore is pre-customer, and says so on the page rather than papering over it. What stands in place of borrowed social proof: what is built, what is certified and to exactly what scope, what is still in progress, and six routes you can use to check all of it without asking us.
Built around the operation, not the software menu
The evidence rule
Four states, kept apart on purpose.
Supported means evidence exists and is named. In progress means a real process is underway and is not finished. Product capability means the software does it and it is not a certification. Not held means we do not have it — and that row stays on the page, because a list of only the wins tells you nothing.
Verifiable, not invented
What is built, what is certified, and what is not.
NEMSIS V3 v3.5.1 Collect Data compliance
SupportedThe NEMSIS Technical Assistance Center issued the Collect Data compliance badge against schema v3.5.1. The scope is stated exactly as issued — one exchange category, one schema version — and is never widened into a blanket platform certification.
NEMSIS 3.5.1 validation in the build
SupportedThe NEMSIS 3.5.1 XSD and Schematron validator modules are present and passing in the ePCR service build. That is a statement about the software, separate from and narrower than the compliance badge above.
HIPAA-aligned controls, under BAA
SupportedAn operating posture, not a certificate. HIPAA has no federal certification programme, so every surface here writes HIPAA-aligned with BAA context and never HIPAA certified.
Native signatures with a verifiable chain
Product capabilitySignature and audit-chain behaviour is built into the platform rather than bolted on, and a signed document can be checked on a public verification page that requires no login. This is product functionality; it is not a third-party badge and is not drawn as one.
Server-authoritative tenant isolation
Product capabilityIn production this application sends no tenant identifier at all — the backend derives tenant from the bearer token. The full control, and its limits, are written out on the security page.
SOC 2 Type II
In progressThe audit engagement is in progress. No completed-audit artifact exists, so nothing here labels the programme complete, and no Type II badge appears anywhere on this site.
DEA chain-of-custody capability
In progressNarcotics chain-of-custody is a platform capability whose compliance evidence is flagged for re-verification. It is not presented as a completed certification or as a fully re-verified posture.
CMS-1500 and 837P construction
In progressClaim document and EDI construction are platform capabilities whose compliance evidence is flagged for re-verification. They are not promoted to a certified state to fill a gap on this page.
Named customer references
Not heldThere are none. AdaptixCore is pre-customer, so there is no logo wall, no case study and no testimonial on this page. When a real reference exists it will arrive with a named agency, a measured baseline, a measured outcome, the period it covers and the date the customer confirmed the figures — or it will not be published.
Architecture proof
The consolidation is structural, not stitched together for a homepage.
Structural
One operating model, not an integration diagram
Dispatch, documentation, billing, workforce and specialist operations are built as one platform family sharing authorization and audit boundaries. The public site shows that operating chain without attaching performance numbers no benchmark supports.
Audit
Audit behaviour lives inside the platform
Records are hash-chained where integrity matters, and a signed document's chain can be checked from a public page with no account. Audit evidence is a product behaviour here, not a badge reconstructed afterwards.
Validation
Standards stay pinned to their exact scope
NEMSIS, billing-format, security and compliance language is bounded by what the evidence actually supports. Pending work stays pending, and an unsupported metric stays off the page rather than being softened into one.
Claims, with their evidence attached
Each claim carries its own qualification and date.
These are rendered from the platform's claims evidence registry rather than written as copy beside it, so the page cannot drift from the evidence. A claim without current evidence does not soften — it disappears. The full compliance state, including the frameworks AdaptixCore does not hold, is on the security page.
- Supported
NEMSIS V3 Compliant
v3.5.1 Collect Data
Issued by the NEMSIS Technical Assistance Center for the 'Collect Data' exchange category against NEMSIS schema v3.5.1. This is a data-exchange compliance badge for that category and schema version, not a blanket certification of the platform.
Evidence confirmed 2026-08-13 · re-verify by 2027-08-13
- Supported
NEMSIS 3.5.1
Built into the ePCR software
Internal build verification: the NEMSIS 3.5.1 XSD/Schematron validator modules are confirmed present and passing in the ePCR service. This is a statement about the software build, not a claim of formal third-party NEMSIS certification.
Evidence confirmed 2026-04-30 · re-verify by 2026-10-30
- Supported
HIPAA
Aligned
Operating posture only. HIPAA has no federal certification program, so "HIPAA-aligned" (not "HIPAA certified" or "HIPAA compliant") is the accurate framing per the project's own public-copy rule.
Evidence confirmed 2026-08-04 · re-verify by 2027-02-04
- In progress
SOC 2 Type II
In progress
Audit engagement described as in progress. No completion evidence or completion date is confirmed anywhere in this repository as of the audit date below.
Evidence confirmed 2026-08-04 · re-verify by 2026-11-04
Check it yourself
Six routes that do not require taking our word for anything.
Who runs on it
We are pre-customer, and we say so plainly.
There is no logo wall on this page because there is nobody to put on it yet, and a pilot conversation is presented as a next step rather than retroactively turned into traction. If you want the security and legal pack before that conversation, it is all in the trust centre.