Implementation
A proven path to successful go-live.
Nym’s implementation process establishes the coding standards, technical workflow, validation criteria, and governance model necessary to build trust before autonomous coding goes into production.
Configure. Validate. Prove. Then automate.
A health system should not route codes assigned by AI directly to billing because a vendor says the technology is ready. Accuracy, workflow, coding logic, exceptions, and technical performance should first be tested against defined criteria.
Data Collection
During the pre-kickoff phase, Nym will collect any coding-related customer data and information that is needed to correctly configure the engine. The goals in this phase are two-fold:
- Collect all requirements for engine customization, including site or payer-specific guidelines and SOPs, to enable the engine to replicate your current coding practices.
- Collect a set of historical charts representing recent encounters from in-scope facilities, as well as the associated coding data for those charts. This information is used to configure the engine to the health system’s specific chart format. Additionally, the information is used to check the accuracy of the engine customization throughout the implementation process to ensure it produces results that align to your coding practices.
Discovery
The first phase of implementation with Nym is focused on discovery. Nym will review all documentation received in the Pre-Kickoff phase as well as arrange a series of activities and discussions to ensure that we have a complete understanding of your coding practices and engine customization requirements. This will culminate in an audit, with Nym’s team manually coding a set of charts and asking for your feedback, as a final check before engine configuration begins.
During this phase, we will also work with the technical team to design the full production flow. We’ll share examples of how we’ve set up the integration with other clients, and work with you to customize the flow based on your systems and operations. The workflow will be designed to ensure that we meet our 12-hour turnaround time (TAT) commitment.
Build and
Configuration
The second phase of implementation with Nym is focused on the configuration and integration of Nym’s medical coding engine. During this phase, Nym configures the engine according to the customer’s coding practices and other requirements defined during the discovery phase. Nym will use the historical charts provided to test the configuration and ensure that it is producing the intended results.
During the configuration and integration phase, the technical teams will build the technical integration as designed during the discovery phase.
User Acceptance Testing
The third phase of implementation with Nym is focused on user acceptance testing (UAT). The customer begins sending Nym its daily discharge medical records from each in-scope facility, which then get coded by the Nym engine. Before being sent back to the customer, a random subset of medical records coded by the Nym engine is audited by Nym’s auditing team, with the goal of identifying and remedying any critical errors and compliance issues.
During this phase, the technical integration is also tested to ensure it works as intended.
Once all go-live criteria have been met, including reaching 95%+ accuracy (based on the UAT audit) as well as 12 hour turnaround time (as defined during the technical integration), we will jointly identify a go-live date.
Fully Automated
Coding
After phase three is complete and the service start date begins, Nym’s medical engine is working full time, automating coding for the customer. Nym and the customer will regularly evaluate coding accuracy of Nym-coded charts to ensure that they continuously meet or exceed a 95% accuracy threshold overall. Once live, Nym expects to automatically code 50%-70% of complete records with no human intervention (specific coverage varies per specialty).
Go-live is a milestone, not the finish line.
Once in production, Nym supports the coding logic and technology behind the engine while health systems retain visibility into performance, accuracy, coverage, exceptions, and outcomes. Coding guideline updates are incorporated into the engine, and regular performance reviews create a clear path for ongoing AI governance and expansion.
The people that make autonomous coding go-live a success.
A smooth implementation process requires specific resources from the customer, and none are more important than the people. Below are the people and teams on the customer side whose involvement is vital to ensuring the successful implementation of autonomous coding with Nym.
Project Champion
Coding Lead
Technical Project Manager
Technical Team
Frequently Asked Questions
What EHRs does Nym's autonomous medical coding engine integrate with?
Nym integrates with major EHR environments, including Epic, Oracle Health/Cerner, Meditech, and others. The implementation team designs the technical flow around the customer’s environment so records can be processed and coded encounters returned to the existing billing workflow.
How long does it take to implement Nym's autonomous medical coding engine?
Implementation typically takes 3-6 months from contract signing to go-live, depending on organizational complexity and EHR configuration. The process includes technical integration, configuration of Nym’s engine to align with your coding guidelines and workflows, validation testing, and staff training. Most organizations begin seeing measurable results within the first few months, with full ROI typically achieved within 3-6 months post-implementation.
How is Nym's implementation different from computer-assisted coding (CAC)?
Unlike CAC implementations that require extensive workflow changes and ongoing coder training, Nym’s engine operates autonomously in the background without disrupting existing processes. CAC solutions require coders to learn new platforms and review suggested codes before billing, while Nym routes coded encounters directly to billing with zero human intervention. For coding teams comparing coding automation approaches, the difference shows up on day one: no productivity losses, no change management burden, and the freedom to focus on complex cases.
Does Nym's engine require ongoing support or human intervention post-implementation?
Nym’s engine operates autonomously without requiring human intervention for successfully coded encounters. While no regular support is needed from the customer for daily production, Nym maintains contact with a point person on your team for rare troubleshooting needs and meets with customers on a regular basis to provide updates on coding performance and discuss additional needs, including adding new specialties and facilities. Our team handles all technical updates, including coding guideline changes and system maintenance, ensuring continuous operation.
Explore the latest from Nym
