A Nine-Day Gap With Real Consequences
On September 23rd, Hawaii's Office of Medical Cannabis Control and Regulation will take its patient registry offline. The current system, medmj.ehawaii.gov, goes dark for nine days while the state rolls over to a new portal launching September 30th. During that window, patients can view their existing 329 cards, but nothing else moves. No new applications. No renewals. No corrections.
Here's the part that should get every agency IT director's attention: any application sitting in "returned for corrections" status that isn't resubmitted and approved before the cutover gets deleted. Not paused. Not carried forward. Deleted. Patients in that limbo have to start over from scratch once the new system goes live.
This isn't a criticism of Hawaii's staff, who are clearly trying to manage a hard problem and have told applicants to submit by September 16th to avoid getting caught in the gap. It's a look at what happens by default when a registry migration doesn't have a governed way to carry records through a system change.
A record that gets deleted during a system cutover isn't a technical footnote. For the patient on the other end, it's a form they have to fill out again, a wait they have to sit through twice, and a card they don't have while they wait.
Why This Keeps Happening
Registry platforms accumulate years of records, custom fields, and one-off exceptions that nobody documented well. When a state decides to swap the platform underneath, the safest technical move often looks like a hard cutoff: freeze the old system, load the new one, pick a date and go. It's simpler to build and easier to test. It's also why in-flight records become the first casualty.
South Dakota's medical cannabis registry has dealt with similar growing pains without a full platform swap, just steady enrollment increases that stress-test intake and processing capacity. Georgia went through something comparable this year when nearly 10,000 patients joined its registry within weeks of an eligibility expansion, creating a four-week card wait. Volume spikes and platform migrations are different problems, but they share the same root cause: systems that weren't built with enough slack, or enough visibility, to absorb change gracefully.
What governed intake actually changes
A governed integration approach doesn't eliminate the need for a cutover date. It changes what happens to the records caught in between. Applications in a correction state aren't just sitting in a database table waiting for someone to remember them before the deadline. They're tracked through a defined lifecycle, queued, in review, awaiting resubmission, with a timestamped audit trail that shows exactly where each one stands and how long it's been there.
That visibility is what lets a program manager make a real decision instead of a default one. If 200 applications are stuck in corrections a week before a cutover, someone can see that number, triage it, and extend outreach to those specific patients rather than letting a system rule quietly delete them.
Building the Bridge, Not Just the New System
AIRLIFT Connect handles this kind of transition as an integration problem, not a lift-and-drop. Capture keeps pulling in signed forms and inbound requests during the migration window instead of freezing intake entirely. Transform maps records from the old schema to the new one, so a patient's history doesn't just disappear because two systems structure a date field differently. Deliver moves the completed record into the new registry, and if that delivery fails, it's isolated and retried instead of silently dropped. Observe tracks every one of those records through the whole process, so nobody finds out about a lost application from an angry phone call.
None of that requires slowing down the target launch date. It requires deciding, ahead of time, that in-flight records get carried through rather than treated as acceptable loss. That's a governance decision as much as a technical one, and it's the kind of decision that's much easier to make when you're evaluating a vendor before a migration than when you're three weeks out from a hard deadline.
Hawaii's team will get through this transition. Most patients will resubmit in time, and the new portal will probably work fine on day one. But the deletion clause in that migration plan is worth remembering the next time your agency scopes a system replacement. Ask the vendor what happens to a record that's mid-review on cutover day. If the honest answer is "it gets deleted," that's not a small detail to fix later.
cloudPWR builds AIRLIFT Connect specifically for agencies that can't afford to treat in-flight records as disposable, whether that's a cannabis patient registry, a licensing system, or any other high-volume intake process. If your agency has a platform migration on the roadmap, it's worth talking through before the cutover date gets circled on the calendar, not after.