Repair mismatched patient IDs
Use current CharmHealth exports to prove which BHW Record ID belongs to each patient. CrewHQ will preview complete swaps and moves, preserve registry-only records with the patient, and block any repair that could strand clinical or portal data.
1 � Select authoritative CharmHealth exports
Preview requiredCharmHealth Record IDs stay authoritative. CrewHQ never invents a BHW number. A current registry occupant must have a verified destination in the same files before a swap can be approved.
EncounterStatistics CSV files
Select the same complete monthly file set used for patient loading. Exact duplicate files and repeated patient rows are removed locally before the protected comparison.
2 � Review every proposed move
Not reviewed| Result | CharmHealth ID | Current registry ID | Patient | DOB | Why |
|---|
3 � Resolve a blocked registry occupant
Verification requiredChoose the verified next identity for the current CrewHQ occupant. Enter an exact canonical BHW#### shown in CharmHealth, or place the occupant under a clearly non-canonical temporary number while the patient is reenrolled. A temporary number cannot open the portal or be used as a final BHW Patient ID.
Resolutions stay only in browser memory until the protected preview. The exact temporary or CharmHealth destination is bound to the signed approval and counted in the audit; names and dates of birth are not written to the audit event.
4 � Apply only approved repairs
Atomic protected writeBlocked rows never change. A temporary holding move remains blocked when encounters, a Blueprint, check-ins, consent, portal access, or other protected links require a separately approved migration.
Approval expires after 15 minutes. Eligible transactions move Patient Master, primary contact, identifier, and coverage records together or write nothing.