EMR

Bed Assignment Now Displayed in Patient Header

What's New

The patient chart header now displays the assigned bed alongside the building and room. The header now reads as: Service Facility → Building → Room → Bed in a single, consistent line at the top of every patient chart.

Why This Matters

Locating a patient quickly is critical during emergencies and routine care operations. Without the bed displayed in the header, staff had to leave the chart and manually scan the bed board to pinpoint a patient's exact location. Surfacing the bed directly in the header eliminates that extra step, reduces response time, and gives care teams a complete picture of patient placement without navigating away from the record.

Who It's For

Direct care staff, nurses, admissions representatives, operations leads, and any role that needs to physically locate a patient or verify placement from within the chart.

How it works

Navigate: Patient Chart → top header bar (Service Facility / Building / Room / Bed line)

Steps:

1. Open any patient chart via Search Patients, Census, or Case Load.

2. View the header bar at the top of the chart, directly below the navigation menu.

3. Confirm the header now reads: Service Facility: [name] – Building: [name] – Room: [name] – Bed: [name/letter].

4. If a bed has not yet been assigned, the field displays "Not Assigned"

5. No additional navigation is required; the bed value pulls automatically from the patient's current bed board assignment.

Open

Incident Reports - View & Delete Controls

What's New

Incident Reports now have a granular, per-user permission model. Two new checkboxes are available on user profiles — Can View All Incident Reports and Can Delete Incident Report — configurable by realm-level admins only. By default, users without elevated permissions can only see and delete their own reports. Realm-level admins retain full view and delete access across all reports in their realm automatically, without requiring the checkboxes to be enabled.

Why This Matters

Previously, any staff member with access to the Incident Reports menu could view all reports submitted by anyone in their facility, including sensitive reports about colleagues, and could delete any report regardless of ownership. This created confidentiality risks, interpersonal exposure, and compliance concerns. The new permission model locks down visibility and delete access to the appropriate people, while preserving admin oversight and keeping a clean audit trail on all deletions.

Who It's For

Realm-level admins (configure permissions); designated staff (elevated view/delete access); all other staff (own reports only by default).

How it works

Navigate: Admin → User Profile → [Permission checkboxes section]

Open

Open

Steps:

1. Log in as a realm-level admin and open the target user's profile.

2. Locate the Can View All Incident Reports checkbox and check it ON to grant the user visibility into all incident reports within their accessible facilities for that realm.

3. Locate the Can Delete Incident Report checkbox and check it ON to allow the user to delete any report they can currently see.

4. Save the profile. The permissions take effect immediately on next access.

5. To restrict access, uncheck either permission and save — the user reverts to seeing and managing only their own reports.

6. To verify behavior, navigate to Incident Reports as the target user and confirm report list contents and delete control visibility match the configured permissions.

Flags/Config:

• Can View All Incident Reports — default Off; User Profile settings, visible and editable by realm-level admins only

• Can Delete Incident Report — default Off; User Profile settings, visible and editable by realm-level admins only

• Realm-level admins have full view-all and delete-all access by default without these checkboxes being enabled

• All permissions are realm-scoped: enabling a permission in Realm A does not grant it in Realm B

Notable Behavior Changes: Users who previously had visibility into all incident reports will lose that access upon deployment if the Can View All Incident Reports permission is not explicitly enabled on their profile. This is a breaking change in default behavior. Realm-level admins should audit existing users and enable the appropriate permissions for any staff who require continued broad access before or immediately after deployment.

Permission Interaction — Delete Scoped to Visible Reports Only: A user with Can Delete Incident Report enabled but without Can View All Incident Reports can only delete their own reports, since reports from other users remain invisible to them. Delete access does not exceed view access.

Incident Reports - Print & Print All

What's New

Incident Reports now support printer-friendly output for both individual incidents and full found sets. A Print button is available on any expanded incident to generate a clean, single-incident print view. A Print All button in the results header generates a multi-page print document covering every incident in the current found set, with each incident starting on its own page. Both print views strip all navigation, filters, search bars, and action controls, producing output optimized for paper and audit use.

Why This Matters

Clinical operations and compliance teams frequently need hard copies of incident reports for audits, reviews, and offline sharing. Previously there was no structured way to produce a clean printed record — users would have had to print raw screen views with navigation chrome and truncated content. The new print output ensures every field prints fully, long text flows across pages without truncation, and attachments are listed legibly, making the output suitable for official records.

Who It's For

Clinical operations staff, compliance officers, admins, and any user who needs printed or paper-ready incident documentation.

How it works

Navigate: Incident Reports → search/filter results list

Open

Print Single:

1. Run a search or locate the incident you need.

2. Click the Print button on that incident.

3. The system generates a print-preview view containing all incident fields — incident ID, type, date/time, service facility, location, reported by, reported on, involved personnel, full additional details text, and attachment filenames.

4. Send to printer or save as needed.

Print All:

1. Run a search with your desired filters to produce a found set of incidents.

2. Click Print All in the results header.

3. The system generates a single print document containing every incident in the current found set.

4. Each incident begins on a new page. If an incident's additional details span multiple pages, it flows naturally and the next incident begins on a fresh page after it concludes.

5. All attachment filenames are listed per incident. Send to printer or save as needed.

Form Builder

Form Comments - Edit & Delete Controls

What's New

Form comments can now be edited and deleted after saving. Comment creators can edit their own comments inline at any time. Admins can edit or delete any comment on any form, with a trash icon appearing exclusively for admin users. Deleted comments are permanently removed from the form view and will not appear on any new exports or prints.

Why This Matters

Previously, a comment entered with incorrect text — or on the wrong patient — was permanently visible on the form and would appear on all printed and exported records, creating clinical documentation errors and compliance risk. This update gives staff the ability to correct mistakes and gives admins a safety net to remove erroneous content before it reaches official records, all while maintaining a full audit trail of every change.

Who It's For

All staff users (edit own comments); Admins (edit or delete any comment).

How it works

Navigate: Any form with comments → inline comment controls

Open

1. Open a form that contains a saved comment or enter one.

2. If you are the comment creator, click into the comment to activate the inline edit control, update the text, and save.

3. If you are an admin, click into any comment to edit it, or click the trash icon to delete it.

4. When deleting, confirm the deletion in the prompt — the comment is immediately removed from the form.

5. New exports and prints will reflect only current, non-deleted comments from that point forward.

6. All edits and deletes are logged automatically in the audit trail (see Audit Logging note below).

Flags/Config: No feature flag. Delete (trash icon) is permission-controlled and visible to Admin role only by default. Non-admins do not see the trash icon and cannot delete or edit another user's comments.

Exports/Print Notes: Only active, non-deleted comments appear on exports and prints generated after a delete action. Previously exported or printed records are not retroactively updated.

Intake

Roles for Intake Process

What's New

Intake form access can now be controlled by EMR user roles. A new Roles for Intake Process flag in Manage Realms switches the permission model for a realm when enabled. All Intake forms now support three configurable access levels — Read and Write, Read Only, and No Access — managed within existing EMR role settings. When the flag is on, individual Intake permission options are hidden from user profiles.

Open

Open

Why This Matters

Previously intake permissions were not form based they were user access based. Role-based permissions let administrators configure access once at the role level and have it apply automatically to every user in that role and for every form. This reduces administrative overhead, improves consistency, and makes access easier to audit.

Who It's For

Realm administrators, EMR role managers, and any staff whose Intake form access is governed by their assigned role.

How It Works 

1. In Master Data>Manage Realms turn on Roles for Intake Process.

2. Review the confirmation popup explaining that Intake form access will be controlled by user roles.

3. In EMR role settings, assign Read and Write, Read Only, or No Access to each Intake form for the relevant roles.

4. Verify that users accessing the Intake process are assigned the correct EMR role — their form access is now driven by that role

Each realm is configured independently — enabling the flag on a parent realm does not affect child realms.

RCM

Statement Delivery Preference & Paper Statement Export

What's New

A new Statement Delivery Preference field can be added to the patient Face Sheet, allowing staff to designate whether a patient receives statements electronically or by paper. A corresponding Paper Statement Export button has been added to Billing → Manage Statements to generate a separate PDF export for paper-preference patients. The existing export button has also been renamed to Export All Statements for clarity.

Why It Matters

Previously, there was no way to flag individual patients for paper statement delivery — all patients were treated the same in statement exports regardless of their actual delivery needs. This created manual workarounds for billing teams managing patients who require printed statements. This update gives billing staff a clean, automated way to separate electronic and paper statement workflows without manual intervention.

Who It's For

Billing and revenue cycle staff responsible for generating and distributing patient statements, particularly at organizations with a mix of electronic and paper delivery needs across their patient population.

How It Works

• Navigate to the patient's Face Sheet → Statement Recipient section and add the form builder component Statement Delivery Preference (which defaults to Electronic or Paper select choices)

•  

  Open

  

   

• The field defaults to Electronic for all patients — there is no blank option

• Patients set to Electronic are included in standard electronic statement delivery runs; patients set to Paper are excluded

• If Electronic is selected and no email address is on file for the patient or surety, the user will see that in the export for the sent statement.

•  

  Open

  

   

• To generate paper statements, navigate to Billing → Manage Statements and click Paper Statement Export to download a PDF of all paper-preference patients only

• The Export All Statements button (formerly "Export Statements") continues to function as before, exporting statements regardless of delivery preference

• Existing patients with no preference on file are treated as Electronic by default

Provider Payment Report now respects "Do Not Send Zero Payments" realm setting

What's new

The Provider Payment Report now correctly filters out transaction lines where the Provider Payment value is $0.00 when the "Do Not Send Zero Payments" setting is enabled in Manage Realms. This filter now applies consistently to both the on-screen report output and the exported PDF. Previously, the realm-level configuration flag was not being respected by the report engine, causing zero-dollar lines to appear regardless of the setting.

Why it matters

Zero-dollar payment lines in the Provider Payment Report create noise that can complicate payroll reconciliation, obscure meaningful transactions, and lead to confusion during audits or provider reviews. When a realm administrator enables "Do Not Send Zero Payments," the expectation is that the report reflects only actionable payment activity.

This fix ensures that realm-level configuration is honored end-to-end — from the on-screen view through to the exported PDF — giving administrators confidence that report output matches their configured preferences.

Who it's for

Realm administrators who have enabled the "Do Not Send Zero Payments" flag in Manage Realms and expect it to suppress zero-dollar lines from provider payroll reporting.

Billing and payroll staff who rely on the Provider Payment Report for accurate, configuration-driven transaction data.

How to use it

If your realm already has "Do Not Send Zero Payments" enabled, the fix takes effect automatically. To confirm the setting is active:

1.Navigate to Manage Realms and confirm the "Do Not Send Zero Payments" checkbox is enabled.

2.Go to Reports > Provider Payroll Report and view a report for a date range that includes known zero-dollar payment activity.

3.Verify that no $0.00 Provider Payment lines appear in the on-screen output.

4.Export the report as a PDF and confirm zero-dollar lines are also absent from the exported file.

Deleted claim lines are now visible, auditable, and exportable

What's new

Two new ways to view and track deleted claim lines have been added to the Billing module. An opt-in "Include Deleted Claim Lines" checkbox on the Posting Report filter bar lets users surface deleted lines alongside active ones which are highlighted in red and included in CSV exports when selected. A new standalone Deleted Claim Lines report in the Billing navigation displays only deleted lines, mirroring the Posting Report's columns plus two new audit columns: Deleted On and Deleted By. Both features are powered by a new audit event recorded each time a claim line is removed from an EOB, capturing the full claim data, deletion timestamp, and the name of the user who performed the deletion.

Why it matters

Previously, once a claim line was deleted from an EOB it was effectively invisible — there was no way to confirm it had existed, who removed it, or when. This created gaps in billing reconciliation and made it difficult to investigate discrepancies or respond to audit inquiries. This release ensures no deleted claim line is permanently lost. Every deletion is captured with a full audit trail, and that data is accessible directly within the reporting tools billing staff already use without requiring a separate support request or database lookup.

Who it's for

Billing staff who need to reconcile payment postings and investigate missing or removed claim lines.

Billing managers and compliance teams who need an audit trail of EOB modifications, including who deleted a line and when.

How to use it

To view deleted lines within the Posting Report:

1.Navigate to Billing > Posting Report.

2.Check the "Include Deleted Claim Lines" checkbox in the filter bar.

3.Apply your date range and other filters, then click Search. Deleted lines appear highlighted in red alongside active lines.

Open

4.Use Export to CSV to download results — the export includes a Deleted On and Deleted By column for deleted rows.

To use the standalone Deleted Claim Lines report:

1.Navigate to Billing > Deleted Claim Lines in the left navigation.

2.Use the same filters as the Posting Report ) to scope results.

3.Review the Deleted On and Deleted By columns to identify when and by whom each line was removed.

4.Click Export to CSV to download the full filtered results including all audit columns.

Open

Open