Migrate your Bp Premier data

Bp Premier supports full patient record exports via Utilities > Export Patient Records, covering demographics, addresses, emergency contacts, and Medicare/DVA details. We map these fields 1:1 and flag any inactive or deceased flags that need downstream attention.

Each consultation is stored as a clinical encounter with date, provider, type (in-rooms, home, phone), and free-text notes. We extract encounter records and preserve the encounter-to-provider relationship via HPI-I linkage.

Clinical notes are stored as formatted text or rich-content blocks. We extract the raw note content and body text; layout and embedded objects may require post-migration formatting review depending on the destination system.

The MySL subsystem stores prescription history with a known date-created quirk: new prescriptions record the prescribing date, while modified prescriptions record the edit date. We flag this discrepancy and log the extraction context so the destination system can interpret prescription timelines accurately.

Appointment Book data includes date, time, duration, provider, appointment type, and status. Historical appointments export cleanly; future recurring appointments may need to be rescheduled on the destination platform if the migration occurs before their date.

Each provider is identified by their HPI-I (Healthcare Provider Identifier – Individual) and linked to their AHPRA registration. We preserve the provider record and their assignment to appointments and encounters.

The practice-level record includes the HPI-O (Healthcare Provider Identifier – Organisation), NASH certificate details, PRODA credentials, and My Health Record registration status. These are essential for re-registering integrations on the destination system.

Uploaded documents (letters, images, referral letters) are stored in a file-store area. We extract and transfer the file store separately, then re-link documents to the corresponding patient record on the destination. File naming conventions and linking metadata must be verified post-migration.

Billing records include item numbers, patient payments, Medicare/DVA rebates, and outstanding balances. We extract the financial ledger as a transactional record; outstanding balances and credit card payment data require explicit re-entry or reconciliation on the destination platform.

Documents uploaded to My Health Record are immutable once submitted and cannot be re-extracted for re-submission to a new system. We document which records were uploaded so the destination system can record the upload reference and avoid duplicate submissions.

Electronic prescriptions dispensed via eRx are tracked in Bp Premier. We extract the dispense history; the destination system must be eRx-enabled to continue the prescription continuity chain.

Practices commonly create custom letter templates with merge fields. We extract the template body and field definitions; the destination system's template engine may use different merge field syntax and requires manual re-authoring.

AI scribe notes generated via the Lyrebird Scribe integration are written back into the clinical note at the time of the encounter. We capture the note content itself during encounter extraction but cannot transfer the Lyrebird integration configuration, which must be re-connected on the destination system independently.

Insurance claim records include carrier details, policy numbers, claim status, and history. We extract claim headers and status; supporting documents and in-progress claims require review before the destination system assumes responsibility.