Software Updates
See Our lastest updates
ACXSS Rebuild Overview
ACXSS Rebuild aims to give a product capable of competing on all fronts.
-
Per client item lists
- Punchout Support
- Non-Owned Clinic Support
- Inventory Rework
- DB / AWS Updates
- Purchase Services
PER CLIENT ITEM LISTS
- This update impacts all ACXSS functionality linked to the products table.
- Code for reports, ordering, inventory, accounting connections, etc., will need reworking.
- Customers can create their own items or build formularies from the public list.
- Direct control for customers over pricing and units of measure.
- API price updates remain functional.
- Item lists accessible for traditional ordering or FFPO.
SUPPORT FOR PUNCHOUTS
Customers will now have control over vendor connections.
- Customers will be able to set vendor type.
This will involve selecting from their list of vendors. Customers can also set up email connections. EDI will remain on the ACXSS side.
- Vendor connections on group, subgroup or member basis.
Punchout for member basis is pending vendor compatibility. The hierarchy is backward, meaning if a member-level vendor connection exists, it will take priority over higher levels.
- Punchout to formulary connection.
Any item purchased through punchout will automatically be added to the group's item list.
INVENTORY REWORK
- One db row per piece of inventory: Previously, ACXSS stored inventory as a single database row for each item or lot number. For example, if you had 5 items and bought 3 more, the row would update to 8. Now, each piece will have its own row—8 separate rows in this instance.
- Complete history / life cycle tracking: This change enables us to track the full history of each piece of inventory, including vendor origin, purchase price, and more. This will result in enhanced inventory reporting.
- Inventory UI rework: The current interface is being streamlined for better usability.
DB / AWS CHANGES
- Upgrading MySQL to version 8
This allows the use of more efficient query styles.
- Tightening EC2 security and replacing old EC2 servers
The current communication server will be replaced with a communication server cluster.
- Employing new AWS technology
For example, the image servers will be retired and replaced with buckets.
- Updating development and production clusters
A big upgrade like this requires new development servers and a database cluster. Upon launch, these will replace the current clusters. Likewise, new production servers will also be deployed.
PURCHASE SERVICES
- Migrate current data to new version / Relabel systems
- Add file uploads to FFPO
- Integrate all systems on group, subgroup or member basis
Stay updated on the latest ACXSS news
- Health System
- Independent Physican Markets
- Community Health Center
- Long-Term Care Facilities
- Corporate Account
- Urgent Cares
- Ambulatory Surgery Centers
- Business Services
- Professional Services
- Consumer Products
- Food & Beverage
- Retail
- Oil & Gas
- Technology
- Public Sector
- Manufacturing
- Small, Midsize & Large Business
© Copyright by ACXSS. All rights reserved. Privacy Policy.