Our support team works from a de-identified patient reference.
Support can work from the de-identified patient reference attached to the shared record. Patient identity remains in your own systems.
Protect the person while preserving the meaning of the work.
Information can be clinically useful without making the direct identity of the person receiving care the organizing principle of the clinical record.
Arcametric holds the structured record of your work while the direct identity of the person stays with you. Separating identity does not remove every privacy obligation, but it narrows what Arcametric can hold.
The architecture
You keep identity. Arcametric helps you record your work.
Your practice or organization Identity stays with your practice or organization
Patient Identity
Name, date of birth, contact details
Identity remains hereEHR
Your existing identity-bearing clinical system
Local Crosswalk
The clinic maps identity to a De-Identified Patient Reference and keeps that link in its own systems.
Privacy boundary
Only these cross De-Identified Patient Reference Structured clinical data Patient identity does not cross
Arcametric De-identified record continues in Arcametric
De-Identified Patient Reference
No patient name required
Structured Clinical Record
Timing, interventions, observations, follow-up
Reports and Analytics
Governed clinical outputs from eligible structured data
Existing data
Patient identity doesn't need to travel with the dataset.
Prepare identity-bearing source information under your control before data enters Arcametric. Accepted records use de-identified references rather than making Arcametric the system that stores the patient's identity.
-
Source records
Identity-bearing information stays under your control
-
Local preparation
Prepare the dataset before it enters Arcametric
-
Excluded identity fields
Names and other identity fields stay outside the hosted dataset
-
Validation
Check admission requirements against Arcametric structure
-
Accepted records
De-identified references enter the structured history
How that works
You keep the names. We hold only a de-identified patient reference.
Each shared record uses a de-identified patient reference rather than a name. You keep the link between that reference and the patient in your own systems. Arcametric stores the structured treatment record associated with that reference.
Your EHR keeps its job
Billing, scheduling, identity, and general charting stay in your existing system. Nothing migrates, nothing integrates. Setup takes minutes, not months.
Arcametric structures the treatment record
Your team records treatment stages, safety events, and outcomes in the same fields every time, so you can report and review them. This is the work your EHR was never built to hold. An interaction reference sits alongside it; your clinical judgment stays in charge.
The identity link stays with you
No field in the shared system can hold a patient's name. You keep the link between the patient's identity and the de-identified patient reference in your own systems.
Your exports stay yours if you leave.
Your exports are yours. The link between each reference and each patient was always in your systems, so nothing about patient identity ever needs to come back from us.
Read this before citing it
See how this architecture helps protect you and your patients.
This page describes the platform's data boundary, not a legal conclusion. No field in the shared system can hold a patient's name. The practice keeps identity; Arcametric receives only a de-identified patient reference and the structured record. That architecture changes what Arcametric stores, but it does not replace legal, privacy, consent, security, or research review.