Configuration drift
Evidence of coverage says one thing. The tables say another. We reconcile benefits, authorizations, and pricing so auto-adjudication can be trusted again.
Practice area
EZ-CAP support, optimization, and implementation
ACM has extensive experience with the EZ-CAP family of products: implementation, configuration, support, and related operations. From 2005 to 2014, ACM principals owned and led EZ-CAP development and still have many of the original technical staff as team members. ACM is an independent consulting and services firm and is not the current software publisher.
What we will say in public
Independent services. Not the current publisher
Clients hire ACM because someone on the call has actually shipped releases, mapped benefits, and sat in a war room when a capitation run failed. That is a services story, not a branding story.
We describe EZ-CAP as the application our clients already license. We do not present ACM as the software vendor, authorized successor, or owner of the platform.
Engagements we take
- New implementation or version move
- Benefits, contracts, and fee-schedule rebuilds
- Auto-adjudication and workflow recovery
- Interfaces, EDI, and companion-guide failures
- Data conversion and parallel test
- Named production support after go-live
Typical work
Where EZ-CAP clients actually get stuck
Go-live and upgrades
Mapping, conversion, mock adjudication, and a rollback plan — with people who have done this on this application, not a generic EHR cutover crew.
The request that sat too long
Letter extract, security role, interface reject, capitation exception. We take the ticket, open the environment, and close it with a note your ops team can reuse.
Name and mark — keep this short
How we treat the name on this site
Federal registration for EZ-CAP as medical accounting software (U.S. Reg. No. 1,656,116, MZI Healthcare LLC) was last maintained during the years ACM principals led the product. That registration later lapsed. Lapse of a federal filing is not the same thing as ACM owning the software, and it is not a license to imply we are the current publisher. Common-law rights can still exist if the name is in commercial use. Counsel should confirm USPTO status before any brand use beyond referring to the application clients already run.
- Use the name to describe the system clients operate (nominative).
- Do not lock it into a logo, product family, or “ACM EZ-CAP.”
- Do not claim the mark was filed while serving as CIO — the original registration dates to 1991. Leadership tenure is 2005–2014, including a renewal cycle.
- Do not compare ACM to “the current owners” on the public site.
Next step
Send the environment, not a novel
Version, last upgrade, the three defects that cost you the most time, and whether you need a project or a retainer. We will tell you if we are the right bench.