Data handling¶
A Business Associate Agreement (BAA) between your organization and Abacus One Group sets our obligations, and no production data is exchanged without one.
Some specifics, such as the retention periods below, can be adjusted for your organization during setup. For security questionnaires and review questions, email infrastructure@abacusonegroup.com.
Minimum necessary¶
The service retrieves documentation only for the visits you want us to load, and our platform receives only what coding the visit needs. Data accessed lists the data, and explains what happens when an ED visit becomes an admission.
What is kept, and where¶
- A copy of what Epic returned for each visit, so that we don't have to ask your Epic system for it again.
- The documentation prepared from that copy for our platform.
- Both are kept in the United States, on HIPAA-eligible cloud infrastructure.
Encryption¶
- In transit: TLS 1.2 or later, for calls to Epic and inside the service.
- At rest: encrypted with keys we control, kept in a managed key service. The documentation retrieved for your organization, and the copy prepared for our platform, have a key of their own.
Separation¶
- Between organizations. Each health system's data, configuration, credentials and audit trail are kept separate, so that a fault or misconfiguration for one organization doesn't expose another's data.
- Between test and production. The service's test environment connects only to your non-production Epic environment and test patients. Production data never enters it.
Access and audit¶
- Least privilege. Each Abacus One staff member, and each part of the service, has only the access the job needs.
- Staff access to production data is limited to named administrators. Every view of patient identifiers is logged, and every action taken on a visit needs a reason and is logged.
- Your audit trail. Epic audits every request under the background user you assign to the service.
- Our audit log. The service records every request it makes to Epic: what was requested, for which encounter, when and with what result.
- No patient information in logs or alerts. Operational logs, metrics and alerts carry internal identifiers only.
Retention¶
The service doesn't keep your documentation long term. Once our platform has received a visit's documentation, the platform's retention applies to it, and the service deletes its own copies on this schedule.
| What | How long |
|---|---|
| What Epic returned for a visit | 30 days |
| Documentation prepared for our platform | Deleted shortly after our platform has received it; 90 days at most |
| The service's record of a visit's status and history | 13 months after its last change |
| Patient identifiers on that record | Removed 90 days after the documentation is delivered |
| Audit log of requests to Epic | 7 years, protected against change |
| Log of staff access and actions | 7 years |
Deletion is automatic, and each deletion is logged.