Welcome to
JD Software
This story starts with BORIM. The Massachusetts Board of Registration in Medicine had originally awarded its licensing modernization project to one of the country's largest system integrators, who attempted a Salesforce-based solution. That effort failed. BORIM then selected JD Software. We reverse-engineered the legacy system, redesigned every workflow, and delivered a platform that reduced physician license processing times by 73 percent. The Executive Director received the Federation of State Medical Boards (FSMB) Award of Merit. The Conference of Boston Teaching Hospitals issued a formal commendation. We succeeded where one of the largest system integrators in the country could not.
That track record is what brought the Massachusetts Department of Public Health (MDPH) to us. The Department needed a unified licensing platform for 28 boards and more than 600,000 active licensed professionals. The transition had to be smooth, with no disruption to public service.
Bringing 28 licensing boards onto a unified platform was not simply a technology project. It was a large-scale organizational transformation that touched every aspect of how MDPH regulates health professionals. The challenges were significant and interconnected.
Timeline
The project had aggressive deadlines from the start. Legacy vendor contracts expired on fixed dates, boards operated on renewal schedules that had to remain in place, and there was no room to disrupt active applications. Every phase had to be sequenced carefully to protect licensing continuity.
Volume
The sheer scale of the initiative was a challenge in itself. MDPH oversees 28 boards, 184 license types, more than 600,000 active licensed professionals, and 25,000 regulated organizations. All of it needed to move onto a single platform without disrupting public service.
Coordination with Subject Matter Experts
Each board operates under distinct statutory requirements, renewal schedules, and unique workflows. Configuring the system accurately required hundreds of working sessions with subject matter experts from every board. Scheduling and conducting these sessions in parallel with ongoing implementation demanded constant coordination.
Rollout Strategy
Deciding how to sequence the rollout across 28 boards was one of the most consequential decisions in the project. A big bang deployment brings all boards live at once, which is simpler for licensees but concentrates all go-live risk in a single event. A phased approach spreads that risk over time but introduces its own complications. In particular, professionals who hold licenses across multiple boards may find themselves having to renew or apply on two different systems simultaneously during the transition period. Neither path is without tradeoffs, and the right choice depends on the agency's risk tolerance and the profile of its licensee population.
Institutional Knowledge Over Formal Documentation
Like most agencies operating legacy systems built over decades, much of the operational knowledge lived with experienced staff rather than in formal documentation. Processes had evolved organically over the years, and the written record had not always kept pace. This is a common and understandable reality in licensing environments where the priority has always been serving the public, not maintaining system documentation. It meant that configuration work required close collaboration with the people who knew the operations best.
Data Migration from 15 Legacy Systems
Consolidating data from 15 separate legacy systems into a single unified platform was one of the highest-risk components of the project. The data spanned decades of licensing activity and was far from perfect. Some records had been carried forward from even older systems that predated the legacy platforms we were replacing, meaning the data had already survived multiple migrations before we ever touched it. Every record still had to be migrated accurately to maintain audit trails and regulatory traceability.
Integrations
The platform required integration with a wide range of national credentialing organizations, examination providers, and state systems. Each integration involved its own API development and vendor coordination, running in parallel with the broader implementation:
How a vendor approaches delivery matters as much as the technology they bring. Too many enterprise software implementations fail not because of the technology, but because of the methodology. Our approach to MDPH reflects 20 years of lessons learned across licensing platform implementations.
Plan the Rollout Strategically
We do not commit to a deployment strategy before understanding the client’s environment. For MDPH, we conducted a structured SWOT analysis with the agency’s leadership, laying out the real advantages and risks of both a big bang deployment and a phased rollout. The pros and cons of each approach were put on the table transparently, and MDPH made an informed decision to go phased. That decision belonged to the client, not to us. Our job was to make sure they had everything they needed to make it with confidence.
The phased approach paid off. Each group of boards that went live generated lessons that were applied directly to the next phase, refining the configuration process, improving training, and sharpening our data migration procedures. By the time the final boards came online, the process was significantly more efficient than when we started.
Drive the Process with JAD Sessions
JD Software does not show up on day one and hand the client a requirements template to fill out. We do not ask agencies to produce comprehensive user stories before we begin. We understand that the people who know how things work are busy doing the work, not writing documentation. Our approach is prototype-driven. In every Joint Application Design session, we lead with a working prototype configured based on our experience with similar boards. The subject matter experts react to something real, tell us what needs to change, and we refine it. This cycle repeats until the configuration meets their needs. It is faster, more productive, and more satisfying for everyone involved than traditional requirements gathering.
Listen to Our Clients
Every agency we work with has deep expertise in how they serve the public. Our job is to listen carefully, understand their operations, and translate that knowledge into a system that works for them. Our domain expertise in professional licensing and regulation means that when we sit down with a board’s subject matter experts, we are not starting from scratch. We understand how licensing boards operate, how enforcement cases flow, how renewals are processed, and how compliance is tracked. Together, we build something better than either side could produce alone.
Get Users Invested Early
Getting users excited about the new system is not a nice-to-have, it is essential to successful adoption. When staff see that the system will genuinely make their lives easier, they become ambassadors for the product. Every JAD session is an opportunity for staff to shape the system. When people see their input reflected in the final product, adoption follows naturally.
Start Data Migration Early
Data porting was one of the most critical workstreams in this project and we treated it that way from day one. With 15 legacy systems holding decades of licensing activity, and some records that had already survived migrations from even older platforms, we knew the data would require significant effort to get right.
We began by loading legacy data into a secured staging environment on AWS, where JD Software and MDPH staff jointly assessed the data structures, identified quality issues, flagged incomplete fields, and documented inconsistencies. From there, we built tailored ETL (Extract-Transform-Load) processes to cleanse, standardize, and map legacy data into the ArcHealth schema. These were not one-time scripts. They were refined iteratively across multiple test loads, with MDPH staff validating that records migrated accurately, key fields aligned with legacy values, and historical data was preserved.
Each phase of the rollout included its own migration cycle, and each cycle made the process sharper. By the time the final boards came online, the ETL processes had been hardened through repetition and real-world feedback. We never assumed the data was clean, and we built the time into the plan to get it right.
Start Integration Coordination Early
Every integration involves external vendors with their own timelines, technical requirements, and approval processes. We catalog all integrations at the start of the project, classify each by criticality and complexity, and begin coordination with external partners as early as possible. Waiting until late in the project to start integration work is one of the most common causes of delayed go-lives.
Invest in Training
Training is not an afterthought. It is a structured program delivered after configuration is complete, so every demonstration and exercise reflects the actual system staff will use on day one. We recognize that a licensing agency's workforce spans a wide range of roles, backgrounds, and comfort levels with technology. Licensees are equally diverse: a 600,000-person population spans every age bracket, and many professionals who are highly skilled in their field may find online systems challenging to navigate. Both groups need to be set up for success.
For internal staff, we deliver role-based, live instructor-led sessions with hands-on exercises in a dedicated training environment. Sessions may be recorded for on-demand reference and to support onboarding of new staff over the life of the contract. Written user guides organized by task serve as durable reference materials that evolve as the system does.
For licensees, we collaborate with the agency to produce short, task-specific video tutorials embedded directly in the portal, covering registration, renewal, account management, document uploads, and complaint submission. These step-by-step videos are designed for users who may be unfamiliar with online systems, reducing the need to call the agency for help and lowering support volume during and after go-live. We also run train-the-trainer sessions for agency staff who will support internal training over time, so the knowledge does not walk out the door when the implementation team does.
Keep Everyone Informed
Internal and external communications are critical to a successful launch. From early in the project, we work with the agency on a communications plan that includes advance notice through existing channels, step-by-step instructions for common tasks, and dedicated support resources during the transition. Both the 350 staff members who process work inside the system every day and the 610,000 licensees who interact with the portal need to know what is changing, when, and what it means for them.
The results speak for themselves. What began as a nine-month sprint to bring 13 boards online has grown into a mature, enterprise-scale platform serving 28 boards and more than 600,000 active licensed professionals across Massachusetts — recognized at the highest levels of state government and by the national professional associations that matter most to our clients.
Industry Recognition
The MDPH implementation team received the Governor’s Performance Recognition Award in both 2023 and 2024 for operational excellence enabled by the new system. The Executive Director of the Massachusetts Board of Registration in Medicine received the Federation of State Medical Boards (FSMB) Award of Merit for the successful implementation. The platform also received a formal commendation from the Conference of Boston Teaching Hospitals for its efficiency, accessibility, and ease of use.
Consolidation of Legacy Infrastructure
Fifteen separate legacy systems were unified into one shared system, eliminating fragmentation while preserving millions of historical license and compliance records along with their associated documentation.
High-Volume Renewal Processing & Public Access
In 2025 alone, nearly 200,000 renewals and over 61,000 new licenses were processed within the system, alongside thousands of complaints, record requests, and incident reports.
With over 1 million public document downloads annually and 4 terabytes of stored documentation, the platform demonstrates consistent performance under continuous public access and high data volume.
Improved Security & Compliance
The platform is hosted in AWS GovCloud, a FedRAMP-compliant environment designed specifically for government workloads with strict data residency and access control requirements. ArcHealth is SOC 2 Type II certified and HIPAA compliant, with standardized authentication controls and multi-factor verification enforced across all user access points. These certifications are not checkboxes — they reflect the security posture required to protect the health licensure data of more than 600,000 professionals.
The architecture is built for continuous availability. ArcHealth runs on a high-availability infrastructure with automated failover, eliminating single points of failure. A comprehensive disaster recovery plan ensures that in the event of a serious incident, the system can be restored within defined recovery time and recovery point objectives. For an agency that processes renewals year-round and cannot afford system downtime, this is not optional infrastructure — it is the foundation the platform is built on.
The story did not end with the final phase. It never does. Implementation is not a finish line for us — it is the beginning of an ongoing partnership. We meet with MDPH on a weekly basis to review operations, surface issues, and plan what comes next. New releases ship practically every two weeks, each one carrying improvements driven by direct feedback from staff and operational experience on the platform. Regulatory changes, new license types, evolving workflows — these are absorbed into the system continuously, without disruptive rebuilds or emergency projects.
This is what a long-term partnership looks like. Not a vendor who delivers and disappears, but one that stays at the table, listens every week, and keeps making the system better. MDPH is not running the platform we delivered on day one. They are running something meaningfully better, because we never stopped improving it.
The MDPH eLicensing story is one example of how arc adapts to complex, multi-board environments. To see how it can be configured for your agency, book a demo today.