November 2024 Updates
about 2 months ago by Christina Olinyk
NexHealth continues deepening payment integrations by supporting the customization of payment types. Also announcing enhanced Orthotrac features.
Integration updates
NexHealth's progress towards complete feature parity across all practice management system integrations
- Added Orthotrac support for the following:
API reference updates
Changes to available endpoints including their parameters and content of the response body
- Updates to the create payment transactions endpoint (v20240412 only)
- The
payment_method
field has been replaced withtype_name
- The
- The
payment_type
field has been added to the payment webhook (v20240412 only) - Added dedicated sections to the payments landing page with explainers for how to use
type_name
,transaction_id
andsplit providers and charges
(v20240412 only) - The Adjustments and Charges landing pages have been cleaned up to reflect the current state of the endpoints (v20240412 adjustments and charges only)
- Removed outdated references to
adjustments.accountable_type
/charges.accountable_type
andadjustments.directionality
/charges.directionality
- Added dedicated sections to provide more information on the
includes[]
parameter and monetary values returned in the responses
- Removed outdated references to
- New endpoints to view adjustment type(s) for all types or a payment type by id (v20240412 only)
- Update to the sign of the amount in payments
- We discovered that the new payments view and list endpoints were incorrectly inverting the sign of payment values. These values are now restored to their conventional form where a negative value represents a payment, or put another way, a credit which decreases the patient’s balance due to the office. (v20240412 only)
Developer Portal updates
New features and functionality available in the Developer Portal
- Edit institution details in the Developer portal
- Developers can now edit institution details (name, address, contact email, website) after they’ve been created within the Developer Portal. This replaces the previous suboptimal workflow where they had to contact support or deactivate and create a new institution if they made a mistake.