All resources
Data ownership, and what leaving a system actually involves
Nobody chooses a clinic system by thinking about how they will leave it. That is exactly why leaving is difficult: the terms are agreed at the beginning, when nobody is paying attention to them, and discovered at the end, when there is no leverage left.
Published
Ownership is a contract question
Clinical records belong to the practice and to the patients they describe. That is the professional position and it is not usually disputed. What varies — enormously — is whether the contract you signed says so, and what practical access it grants you while the agreement is running.
A vendor can agree that you own the data and still hold it somewhere you cannot reach without asking. Ownership without access is a sentence in a contract, not a capability.
An export is not a migration
These two words are used interchangeably in sales conversations and they describe completely different amounts of work.
An export is your data, out of the system, in a format something else can read. A migration is that data arriving inside another vendor's system, mapped to their fields, with the parts that do not correspond either transformed or consciously abandoned. The first can be a feature. The second is a project, and it is priced like one.
When a vendor says you can leave whenever you like, ask which of the two they mean, and who does the work.
The attachments are where it goes wrong
Structured fields — names, dates, diagnoses, appointments — are the easy part. What routinely fails to travel is everything that was attached rather than typed: scanned referrals, consent forms, photographs, letters, uploaded results.
Ask specifically whether documents come out with the records, whether they stay linked to the right patient and encounter, and in what form. A folder of files with machine-generated names, detached from the records they belonged to, is technically an export and practically a loss.
What to settle before you sign
- Can you produce an export yourself, on a normal working day, without raising a request?
- Does the export include documents and attachments, still linked to the right record?
- Is the right to that export written into the agreement, or only described in a meeting?
- If the relationship ends badly, does anything about your access change?
- How long is your data kept after you leave, and what evidence do you get that it was deleted?
Our own answer, and its limit
SkyEagle HIS & EMR runs on an open database, and you can export your records yourself. You also have access to the database underneath, which is unusual enough to be worth stating plainly.
The limit matters as much as the capability: that is access, not a migration service. If you decide to move to another vendor, mapping and loading your records into their system is separate work that has to be inspected and quoted. We would rather write that here than let it be inferred.
Where to go from here
Every SkyEagle product line can be seen in a walkthrough, with its scope and any configuration or integration requirements explained.