What it is
- It runs beside the records you already keep.
- It structures the full arc, from preparation through follow-up.
- It turns routine documentation into report-ready output.
- It holds de-identified patient references rather than patient names.
When information crosses a boundary, trust must travel with it
A clinical record may be created for one purpose and later become relevant to another. The question is not simply whether information can be exchanged, but whether its meaning stays intact and its use stays appropriate after it moves beyond the people and systems that first held it.
Separating direct identity from structured clinical work can reduce unnecessary exposure. It does not, by itself, make information legally de-identified, exempt from privacy law, or available for secondary use. Those duties depend on the information, the parties, the purpose, and the governing legal framework.
What it is, and where it stops
See exactly where Arcametric stops.
The fastest way to know whether Arcametric fits is to see exactly where it stops. It measures and documents. It does not direct care.
What it is not
- It does not use artificial intelligence (AI).
- It is not an electronic health record.
- It is not a billing or scheduling system.
- It does not direct care or make treatment decisions.
- It makes no claim to improve clinical outcomes.
Why it is different
Zero-PHI by design
This is the part that is hard to say in words and easy to see in a picture. Privacy here is not a policy written on top of the software. It is the shape of the database.
What it means
What Zero-PHI makes possible
The architecture is the mechanism. These are the consequences it creates for the people who use it and the people who review it.
