Betasky

Chapter 17: Migration Glossary


Chapter Overview

Terms used across this migration guide.


Terms

TermDefinition
Tier A (Operational)Structured data for go-live census: one current episode, meds, forward schedule in Betasky
Tier B (Registry)Every patient record + intake — active and discharged
Tier C (Archive)Historical episode PDFs + registered archive visits
Archive visitCompleted visit on an episode timeline, created from an uploaded visit or OASIS PDF — for history lookup, not live editing
Archive extractionBetasky reads PDF metadata (type, date, signer) after upload to a migration care order
Schedule ActivityAxxess Patient Chart task list — primary source for OASIS and visit note PDFs
Migration care orderHistorical episode shell (creation_source = MIGRATION) for archive lookup
Go-live episodeCurrent cert period where staff schedule and document new care in Betasky
Cutover dateDay Betasky becomes system of record; drives status and episode curation
CurationJoint session to pick one true current episode per active patient — ignore Axxess chaos
WaterfallImport order: reference → staff → patients → clinical → archive PDFs
Validation importTest run after zip review — reports results before final Production load
Migration zipSingle secure package with all exports from Chapter 5 — starts the 2-week clock when accepted
MRNMedical record number from your legacy EMR
Profile PDFAxxess patient chart print → intake data
Med Profile PDFAxxess medication list print → med list + reviews
Employee ListAxxess Report Center export — staff with email, Title, Credentials, and Role (permissions)
Example AgencyFictional agency used in Part IV to illustrate the process
Self-service / Guided / White-gloveWho runs exports, mapping, and validation (Chapter 1)

Related documentation


End of Migration Guide