Getting a stalled patient portal moving again
How we rescue stalled healthcare IT projects and still deliver a compliant patient portal.
This is an example of how we work, using an illustrative company. It shows our approach, but it isn't a specific client project.
The challenge
Healthcare providers often see an outside-built patient portal stall. After a long stretch of work, the project is behind schedule, over budget, and the software doesn't meet NEN 7510 security requirements. Boards start thinking about pulling the plug.
Our approach
First we look at how much of the existing software is still usable. Then we assemble a team with both healthcare IT and NEN 7510 experience, and work toward a fully working, compliant portal on a tight timeline.
Review
First phaseWe review the software and the security, and talk to the people involved to find the core problems.
Recovery plan & team
NextA go/no-go call, a recovery plan in short sprints, and a team with healthcare IT experience.
Rebuild to NEN 7510
Main phaseWe rebuild the security layer, the EHR connection via HL7 FHIR, and the patient-facing features.
Review, training & go-live
Wrap-upA NEN 7510 review, testing with patients and care staff, training, and a phased launch.
What this approach delivers
The approach delivers a working portal that meets NEN 7510 and connects to the EHR via HL7 FHIR. Typically more patients use the portal, phone traffic drops, and satisfaction goes up. What it delivers depends on the state of the existing project and how ready the organization is to change.
Technologies used
Related articles
Ready to make one process smarter?
Tell us where your team loses time. We turn it into practical automation ideas and a safe first step.