The platform landscape
The Allscripts/Veradigm portfolio includes distinct product lines such as TouchWorks EHR and Professional EHR on the ambulatory side and Sunrise in the acute setting. These were built differently and audit documentation activity in different ways. A discovery request that does not first establish the specific product risks asking for reports that the deployed product does not generate — and accepting an objection that is really about the wrong product name.
Audit trail & access-log reporting
- Product-specific audit log
- Each Allscripts/Veradigm product maintains its own audit of user actions and documentation activity; the report names and scope differ by product line.
- Document version / edit history
- Versioning and edit timing for clinical documentation, where the product captures it.
- Access reporting
- Records of which users accessed the chart, used to place users in the record around a disputed event.
Report names and behavior vary by version, module, and how the organization configured its system — capability should be assessed against the specific deployment, not assumed.
| Timestamp (UTC) | User | Action | Detail |
|---|---|---|---|
| 2024-03-11 22:47:03 | RN J. Doe | CREATE | Progress note created — status: draft |
| 2024-03-11 23:02:10 | RN J. Doe | VIEW | Vitals flowsheet opened |
| 2024-03-12 08:55:41 | Dr. A. Roe | VIEW | Progress note opened |
| 2024-03-12 09:14:55 | RN J. Doe | EDIT | Flagged: Progress note edited — entered late, back-dated to 03-11 |
| 2024-03-12 09:15:10 | RN J. Doe | SIGN | Progress note signed |
What to demand in discovery
- Establish the specific Allscripts/Veradigm product (e.g., TouchWorks, Professional EHR, or Sunrise) before drafting report-specific requests.
- Request the audit log for that product by function — access, documentation actions, and edit history — rather than a generic 'audit trail' that may not match the product's terminology.
- Ask for document version history and edit timing where the product supports it.
- Confirm the version, since audit behavior can differ across releases within the same product line.
Common production gaps
- Drafting requests against the wrong product, inviting a technically-true objection that the named report does not exist.
- Accepting an access report from one product line as equivalent to change history from another.
- Missing document version history because it is reached differently than the primary audit log.
- Overlooking that an acute (Sunrise) and ambulatory (TouchWorks/Professional) deployment at the same health system may both be relevant and audit separately.
Frequently asked questions
Is Veradigm the same as Allscripts?
Veradigm is the current brand for what was Allscripts. The underlying products — such as TouchWorks, Professional EHR, and Sunrise — carry forward, and each audits documentation differently, so identifying the specific product remains the key step.
Why does the right discovery request depend on the Allscripts product?
Because the product lines were built separately and use different audit reports and terminology, a request drafted for one product can be answered with a valid 'that report does not exist' for another. Establishing the deployed product avoids that dead end.
What if a health system uses more than one Allscripts product?
It is common for an acute product like Sunrise and an ambulatory product like TouchWorks to coexist. Each audits separately, so both may need to be addressed depending on where the disputed care was documented.
This page is technical and regulatory information, not legal advice.