Data and Privacy
How Assurlytics documentation handles data: examples are non-PHI, and no patient data is published here.
Documentation draft — not a verified product specification. This page states the Release 1.0 product restriction from the source document. It does not claim any compliance certification.
Overview
This documentation site publishes no patient data and no patient-identifiable information. All examples are illustrative and non-PHI.
Release 1.0 workflows are intended for structured, non-PHI inputs only.
What not to enter
Do not input identifiable patient information into any Assurlytics field, chat, extension or uploaded material. This includes patient names, dates of birth, member IDs, medical record numbers, addresses, phone numbers, patient-specific clinical records, and combinations of details that could identify a patient.
In particular, do not paste real patient charts, claim screenshots containing identifiers, EOBs with member information, or clinical narratives that could identify a person.
Privacy-first examples
Use fictional, general or publicly available reference data. Acceptable examples include an ICD-10-CM code, a payer's public name, a state, or a generic claim scenario without an identifiable individual.
In Denial Help, clinical context must be generalised and non-identifying only — never identifiable patient history, diagnoses tied to a specific individual, chart extracts, dates of birth or member numbers. See Denial Help.
In Payer Intelligence, do not enter member IDs, dates of birth, patient names or other patient identifiers. See Payer Intelligence.
Human-in-the-loop decision support
Assurlytics can help explain and organise research. The professional user must independently confirm code selection, payer rules, documentation requirements, medical necessity and submission decisions.
No unsupported compliance claims
Do not claim HIPAA compliance, SOC 2 certification, a signed BAA, encryption standards, specific retention periods or data residency unless formally verified by legal/security and published product policies. Not processing PHI is a product restriction, not proof that all regulatory obligations are eliminated.
Similarly, do not imply that History is private, encrypted, deleted automatically or excluded from AI training unless verified by published product policy and implementation. See Dashboard and History.
Source and code-set accuracy
Check code set, version, effective date and official reference. Payer policies and code descriptors can change. Certain content may be licensed; do not republish copyrighted code descriptions or proprietary payer content without permission.
Reporting inaccurate answers
If the application returns a wrong code set, fabricated source, inaccurate payer ID or questionable AI explanation, do not rely on it. Report the issue through the actual support channel once published. See Contact Support.
Principles used in this documentation
- Use only verified, non-PHI examples.
- Do not copy real claims, denials or patient records into documentation examples.
- Follow your organisation's privacy and compliance rules when using the live application.
If you need help with a real case
Use the live application through your organisation's approved process, and do not paste patient information into documentation feedback, support messages sent from this site, or public channels.