Services

Epic is the conversion everyone is asking for. We still do the rest.

Independent consulting for practices mid-conversion, mid-upgrade, or stuck with an interface the state keeps rejecting. Remote-first, on-site when go-live needs a body in the room.

Epic and EHR conversions

The current demand is Epic: health systems consolidating acquired clinics, ambulatory groups leaving NextGen or Greenway, and organizations that need history in Epic that clinicians will actually open. We extract, map, and load what Epic’s conversion specs will take — problems, medications, allergies, immunizations, documents, appointments, charges, future orders.

Complete conversions to and from Epic, NextGen, Greenway, Allscripts, Amazing Charts, SoapWare, Siemens Signature Gold, related practice-management systems, and any software that resides in a database. Typical work: source analysis, field mapping, trial loads, exception lists, and cutover support. Spreadsheet-only conversions are how history disappears. We do not do those.

Mirth Connect / NextGen Connect

Custom channels in JavaScript and SQL. HL7 where it belongs, file and SFTP where that is what the other side will take, FHIR when the EHR actually exposes it.

PDMP — prescription drug monitoring

Every state PDMP (often via Bamboo Health / PMP InterConnect or a state gateway) expects a clean query before a controlled-substance script goes out. Out-of-the-box EHR PDMP fails on identifiers, gateway credentials, patient matching, and the audit trail the board will ask for later.

We put Mirth in the middle: normalize the query, map MRN/NPI/DEA the way that state wants, log the response, and surface NACKs instead of a silent miss. Clinics keep prescribing without a second browser and a hope.

State immunizations (IIS)

Each state’s Immunization Information System wants HL7 VXU — usually CDC 2.5.1 — with CVX/MVX codes, VFC eligibility, and either SOAP/WSDL or MLLP. Bidirectional shops also send QBP queries so the chart can show what the school and the health department already know.

The EHR’s “immunization interface” is almost never the message the IIS will accept. Mirth uplifts, validates, retries, and reconciles ACKs so promoting-interoperability and VFC reporting do not fail in a queue nobody watches.

Cardiac devices — IDCO pacemaker / ICD

Programmers and remote monitors (Biotronik, Medtronic, St. Jude and others) emit IHE IDCO HL7 — implantable pacemaker, ICD, CRT, and loop-recorder interrogations. We built a production Mirth path that files those observations into the EHR, matches the patient, splits remote vs in-clinic traffic, and opens a usable encounter instead of dropping a PDF on a share. Details on Work.

Also: labs, billing, pharmacy, appointment reminders, grant extracts, and the vendor that will only take a CSV at 2 a.m. We write, troubleshoot, and hand off channels you can operate — or we stay on to keep them healthy.

NextGen EHR and EPM — pre-KBM through KBM 8

Joshua has been in NextGen since the 1990s — pre-KBM through the latest KBM 8. KBM and EMR upgrades, go-lives, med/CPT/ICD updates, templates (including a custom wound-care suite: multi-wound grid, measurements, treatments, Wagner grade, close-wound, and a note that writes from the grid), documents, File Maintenance, Blobulizer, Rosetta, BBP, Dragon, DAX, and Nuance. Reporting in SSRS and Crystal. Stored procedures, jobs, and SSIS packages written against the real schema, not a diagram in a vendor deck.

The SQL tables are working memory: person and encounter, orders, documents, insurance, the KBM assessment libraries, the odd join that is the only way a conversion finds historical vitals or signed notes. That is why Epic (and other) conversions off NextGen do not start with a guess about where the data lives.

Hospitals, IDNs, FQHCs, and specialty groups — cardiology, orthopedics, ENT, dermatology, pediatrics, family medicine, behavioral health — from a single provider to more than a thousand. Surrounding stack: Soarian Clinicals, i2iTracks, Phreesia, Birdeye, fax, Citrix, and terminal services.

Reporting, SQL, and ServiceNow

Operational and clinical reports written straight to the NextGen SQL database — including NCQA / HEDIS-style diabetes scorecards with targets and exception highlighting, and an SSRS archive so a converted clinic can still find and print the old chart after the source EHR is off. ServiceNow support at clinics that already run it. NextGen certified (2025) and ServiceNow certified (2025).

Custom software

When there is no product for the workflow — a local operations desk, a mobile app, a one-off extract — we build it. See selected work. Healthcare remains the core practice; custom software is how we finish jobs the EHR will not.

Ask about Epic, PDMP, or a conversion