Claim status for 33 branches, checked by logging in to each one over VPN
Each branch's National Health Insurance (NHI, Taiwan's public health insurer) claim status lived only in that branch's local hospital information system (HIS). Checking it meant connecting to each branch over VPN and paging through screens by hand, so headquarters had no real-time view. Newer versions of macOS had even removed the built-in L2TP VPN, so logging in by hand was becoming impossible too.
- Client
- Same group, headquarters · HIS at 33 branches
- Scope
- Legacy system integration
- Key result
- Monthly branch checks → fully automated
The problems we found
- Whether claims were filed on time, or rejected, was locked inside 33 separate local legacy systems
- Monthly manual VPN checks, one branch at a time, left headquarters with no real-time view
- Once the operating system dropped L2TP support, even logging in by hand was becoming impossible
What we changed
- A full VPN tunnel built inside a Docker container. None of the existing equipment at the 33 branches had to change
- Browser automation inside the container logs in to each branch's HIS and pulls the claim details
- The 33 branches run in sequence automatically, about 15–30 minutes end to end, with results written to a central cloud database
- It can be scheduled to run monthly, so headquarters opens the dashboard and sees every branch's status
Results
- For the first time, headquarters sees claim status and exceptions for every branch on one screen
- Monthly branch-by-branch checks → fully automated
Many people assume only cloud systems can be automated. Legacy systems you can't modify, and data locked behind an internal network, can be handled too.
Is some of your data locked in an old system you can't change?
Start with a free 30-minute call about how the work runs today, and we'll judge whether a closer look is worthwhile. Finding where it really gets stuck means looking at the actual workflow.