Planned
Transfer intent exists.
BestCura · TRANSFER INTEGRITY
TRANSFER INTEGRITYA transfer is more than a new facility ID.
During transfer, facility, jurisdiction, professional authority, rules and work state can change meaning at once. BestCura makes that a traceable state transition rather than a silent context switch.
Technology should carry complexity so people can give their attention to people.
THE HUMAN AT THE CENTER
A transfer is not a facility-ID change. For a person, it is a transition of responsibility.
When a patient moves between facilities, teams or jurisdictions, it must be clear which context still applies and which one has become effective. BestCura separates transfer intent from transfer effective and treats the transition as a governed state change.
COMMIT INTEGRITY
Intent and effective are different states.
Arrival alone does not automatically make target context the new execution basis.
Authorized
Transfer authority is checked.
Arrived
Patient has arrived while target context may still be unresolved.
Transfer Effective
Confirmed target context moves the execution basis.
A care reality example
Germany → Austria.
Situation
Facility, jurisdiction and bound authority can change.
Conflict
A global reset invalidates too much; a simple facility switch invalidates too little.
BestCura response
BestCura resolves source and target authoritatively and invalidates decision-bound authorizations only when their dependencies are affected.
Outcome
Transfer remains precise, traceable and recoverable.
RECOVERY
A partial transfer must never look complete.
Persisted transfer execution state makes partial execution visible.
Failure Step
The precise interruption point remains recorded.
Reconciliation
Recovery reloads current authoritative state.
No Blind Reactivation
STALE does not return to ACTIVE without dependency revalidation.
Idempotency
Retries must not create duplicate side effects.
FAQ
Frequently asked questions
What is reconciliation?
Re-evaluation of current state after an incomplete transfer. It is not blind resume.
Can rollback simply reactivate old authorizations?
No. Reactivation requires full revalidation of bound dependencies.