Behavioral health archival: Netsmart, Credible, Anasazi and 42 CFR Part 2
In brief
Behavioral-health archival covers the legacy clinical record sets from Netsmart myEvolv, Credible, Anasazi and other behavioral-health EHRs. It adds 42 CFR Part 2 substance-use-disorder confidentiality rules on top of HIPAA, requires stricter consent and disclosure handling, and frequently involves state-specific retention rules longer than general medical records.
Key takeaways
What should readers take away from this guide?
Behavioral-health archival adds 42 CFR Part 2 on top of HIPAA
Stricter consent, disclosure, and re-disclosure rules apply
Common platforms: Netsmart myEvolv, Credible, Anasazi
State retention rules are often longer than general medical records
BytePad supports 42 CFR Part 2 consent capture and access controls
By the numbers
What data defines this market?
Why 42 CFR Part 2 changes the archive design
42 CFR Part 2 is the federal regulation governing the confidentiality of substance-use-disorder (SUD) treatment records. It requires patient consent for every disclosure (with limited exceptions), prohibits re-disclosure without additional consent, and applies stricter audit requirements than HIPAA. An archive holding SUD records must enforce these rules at the record level, not just the user level.
What should a behavioral-health archive include?
Behavioral-health programs keep more narrative content than most medical settings: assessments, treatment plans, progress and group notes, and scanned consents. The archive has to carry each record's consent status and SUD flag forward from the source system, so that the right disclosure rules still apply years after the legacy platform is retired.
- Clinical narrative: assessments, treatment plans, progress and group notes
- Consent records and revocations, linked to the records they govern
- SUD flags that trigger 42 CFR Part 2 handling on every request
- Disclosure history, so re-disclosure rules can be enforced and audited
- Retention dates mapped to the state rule for each program
How does a behavioral-health archival project run?
The project follows the same sequence as any legacy EHR decommissioning, with two extra checkpoints. First, the source system's consent and disclosure model is mapped before extraction, so no SUD record lands in the archive without its controls. Second, release-of-information workflows are tested against Part 2 scenarios during the read-only window, before the legacy platform is shut down. Retention is set per state; see hospital record retention by state.
Which behavioral-health EHRs are typically archived?
Behavioral-health programs most often archive Netsmart myEvolv, Credible and Anasazi, plus a long tail of state-specific behavioral-health EHRs. The trigger is usually the same as in acute care: an enterprise EHR consolidation, after which the legacy platform has to be retired without losing the legal record. Because these systems hold substance-use-disorder treatment records, the archive inherits 42 CFR Part 2 obligations on day one.
Each source is loaded as its own workstream. BytePad ingests it through pre-built connectors and standards-based paths for HL7, FHIR, X12 and free text, with schema validation and record-count reconciliation on every load and chain-of-custody preserved from extract to archive. Scanned consents and narrative notes become searchable through OCR and AI Global Search.
How long must behavioral-health records be kept?
There is no single federal number. Hospital-based programs fall under the Medicare Conditions of Participation floor of at least 5 years (42 CFR 482.24), and state licensing rules are usually longer, commonly 5 to 10 years after discharge or last treatment, with longer periods for minors. Retention is therefore set per state and per record type; see hospital record retention by state or look up a state in the retention lookup tool.
Substance-use-disorder records keep their 42 CFR Part 2 consent and re-disclosure controls for as long as they are retained. Records under litigation hold, audit or open investigation must be excluded from disposition until the hold is released, so the archive has to enforce holds at the record level rather than by system. The disposition process itself is covered in defensible disposition of healthcare records.
What security baseline should a behavioral-health archive meet?
Treat the archive as a production clinical system, not cold storage. The baseline is HITRUST r2, SOC 2 Type II and HIPAA Privacy and Security Rule alignment, with role-based and attribute-based access control, encryption in transit and at rest, and a tamper-evident audit log of every access and disposition decision. Behavioral-health archives add 42 CFR Part 2 consent and re-disclosure controls at the record level, so a user who can open a general medical record cannot automatically open an SUD record for the same patient.
- Record-level SUD flag and consent status carried from the source system
- Role-based and attribute-based access control, enforced on every request
- Tamper-evident audit log of every access, disclosure and disposition decision
- Release-of-information requests fulfilled from the archive with disclosure history attached
Can clinicians see archived behavioral-health records from Epic?
Yes, when the archive is integrated with the active EHR. The common patterns are a Chart Review link into the archive viewer and a SMART on FHIR app embedded in Epic Hyperdrive that calls the archive's FHIR R4 endpoints; both are described in Epic integration for archived data. For behavioral-health content, the archive applies its own Part 2 controls on every retrieval, so the integration does not bypass consent rules that the legacy system enforced.
Sources & references
Where does this analysis come from?
Frequently asked
What questions do buyers ask about EHR archival?
What is behavioral-health EHR archival?
Behavioral-health EHR archival moves the legal record out of a retiring platform such as Netsmart myEvolv, Credible or Anasazi into a read-only archive that keeps the record retrievable for its full retention period. It adds 42 CFR Part 2 consent and re-disclosure controls on top of HIPAA for substance-use-disorder records.
Why is behavioral-health archival different from general medical archival?
Behavioral-health records, particularly substance-use-disorder treatment records, are governed by 42 CFR Part 2 in addition to HIPAA. The regulation requires patient consent for every disclosure (with limited exceptions), prohibits re-disclosure without additional consent, and applies stricter audit requirements. An archive holding these records must enforce these rules at the record level.
Which behavioral-health platforms does InterScripts handle?
Netsmart myEvolv, Credible, Anasazi, and a long tail of state-specific behavioral-health EHRs. Each engagement maps the source system's consent and disclosure model into BytePad's 42 CFR Part 2 controls.
How long do behavioral-health records have to be retained?
Retention is set by state law and record type. Hospital-based programs have a federal floor of at least 5 years under 42 CFR 482.24, and state rules are usually longer, commonly 5 to 10 years after discharge or last treatment, with longer periods for minors. Records under litigation hold are kept until the hold is released.
Do 42 CFR Part 2 rules still apply after the legacy system is retired?
Yes. Substance-use-disorder records keep their consent and re-disclosure requirements for as long as they are retained, so the archive must carry each record's consent status and SUD flag forward and enforce them on every access and release-of-information request.
Related in this pillar
Which related guides should you read next?
How long must hospitals retain medical records?
How long must hospitals keep medical records? The 5-year federal Medicare minimum plus hospital retention rules for 9 states, each with its statute citation.
Read articleDeep Dive · EHR ArchivalDefensible disposition for healthcare data
Defensible disposition for healthcare data: retention schedule, immutable archive, tamper-evident audit log. Three-part OIG/OCR/litigation test.
Read articleTalk to the team that wrote this guide.
Book a 30-minute walkthrough with the InterScripts experts behind this framework. We'll tailor it to your systems, retention obligations, federal compliance posture, and procurement timeline.
Your guide author

This guide is reviewed and maintained by the InterScripts editorial team and reflects current customer engagements, federal program activity, and 2026 regulatory updates.
