Imniren akk

Service Manual

Ldi i tɣuri Sader amnir ummid (PDF) 107 isebtar, 4.6 MB

Amnir n tenfa s tutlayt-ik yettwahyag. Alamma yemmed, ha-t-an s English.

Wagi d amnir n lqem 9.95.2. Ddu ɣer lqem amaynut

Chapter 10Migration from RealLab

This chapter is for the support technician who carries a laboratory's history from the old RealLab program into the program. It explains:

  • What to prepare before migrating, and which files the program accepts.
  • The eight steps of a migration, and what moves and what does not.
  • How to read the acceptance report, and how to undo a migration.

10.1 Before you start

  • The file. A copy of the RealLab database, in one of these forms:
ExtensionWhat it is
.mdb and .accdbA Microsoft Access database
.bakA SQL Server backup file
.mdfA SQL Server data file

It may be 8 GB at most. An Access 97 file cannot be read, so it is first saved in Access as Access 2000 or later (.mdb).

  • Memory. The program works out how much memory the file needs before reading it. If there is not enough, it asks for other programs to be closed.
  • A backup. Migration takes no backup first, and needs none, because either all of it is written or none of it is. But if the program already holds real work, take a backup before migrating (see Chapter 8: Backup and restore).
  • The permission. Import data from a previous system.
  • The time. Migration runs on the server and estimates the time left as it goes. Choose a time when the server will not be switched off.

10.2 The steps of a migration

The page opens from the Settings menu, then Data and continuity, then the Migration from RealLab tab. It also opens from the program's first run. The page has eight steps:

  1. File. Choose the RealLab file from the server's drives, or Or write the file's path. The program searches for RealLab files itself, offers the newest, and stops searching by itself after a minute. If the file is on another computer of the branch, it is uploaded to the server and migrated there, then deleted from it when the migration ends or is stopped.
  2. Preview. Reading the file, changing nothing: the patients, visits and results in the file. If some rows the file says it holds do not come out of it, the program gives their number.
  3. What moves. Choose what moves:
    • The test catalogue and prices: the tests, reference ranges, packages and price lists.
    • Patient files.
    • Visits and their results, with their reports and pictures. They need the patient files and the catalogue.
    • Panel results: blood counts, urine and cultures. They are written on the visits, so they need them.

Under Visits from the year a year is chosen, and the visits before it stay in the old file. The patient files always move, all of them.

  1. Names. The tests in the file whose names the catalogue does not know. For each name: The same as ours, picked from the catalogue, or Another test, created as a new test. A test is never merged with another just because their codes look alike. If the catalogue knows every name, this step is skipped.
  2. Source laboratory. The details of the laboratory the file came from.
  3. Consent. A summary of what moves, and a statement that these are the laboratory's records. If the program already holds work, a second statement is asked, to migrate beside it. Then Bring my data across.
  4. Transfer. You may close this screen: the migration goes on in the program. Do not switch the computer off until it ends; that cuts it, and nothing of it is written.
  5. Result. The acceptance report (see 10.4 The acceptance report).

10.3 What moves and what does not

MovesDoes not move
What was chosen in the What moves stepWhat was not chosen. It stays in the RealLab file and is named in the acceptance report
Every patient file, whatever year was chosenThe visits before the chosen year
The rows that came out of the fileThe rows that did not. If rows are missing, the migration starts only after an explicit statement about it
Prices written as numbersPrices written as text become 0.00, and the report names them

If the program already holds work, the migrated history is added beside it. Nothing is replaced and nothing is merged.

10.4 The acceptance report

After the transfer, the program shows:

  • What is now in the program.
  • What was not brought across, and why.
  • What was left out on purpose, with nothing of it lost.
  • A balance in numbers: what was read from the file, what was brought across, what was not, and what was joined to another. Both sides must agree.

Then Bring in another file for another file, or open the patients to check a few files by eye.

10.5 Undoing a migration

The same page has the section Imports already brought in. An import can be undone while nothing has been done on CLARUS with what it brought.

  1. Press Undo this import on the migration in question.
  2. The program counts what the migration brought and shows what will be deleted. Undoing this import deletes these rows, and only these. What it added to the catalogue stays.
  3. Tick the statement about the deletion, then confirm.

If anything the migration brought has been worked on in the program, the undo is refused and the reason is given.

10.6 When a migration stumbles

What showsLikely causeWhat to do
The file could not be read.The file is damaged, or not of an accepted formTake a new copy from RealLab and try again
A message that the file is Access 97An old form that cannot be readSave it in Access as Access 2000 or later
The file opened, but not one record could be read from it: no patients, no requests and no catalogue. That is what a damaged or half-copied file looks like, not an empty laboratory. Try another copy of the file, or the backup it was made from.The file opened, but it is empty or not a RealLab databaseMake sure it is the right laboratory file
Parts of this file are not what Access wrote. The numbers above are your laboratory, but smaller than it.Parts of the Access file are damagedRepair it in Access, or take a newer copy
A message that rows did not come out of the fileThe file is incomplete or partly damagedTake another copy. If it happens again, it moves only with the statement
A message asking to close other programsNot enough memory to read the fileClose the other programs on the server and try again
The migration could not start.Another migration is running on the computer, or the start failedWait for it to end, then try again
The migration was cut and nothing of it was written.The program was closed or the server switched off during the transferStart again, and do not switch the server off until it ends
Mmel-d tuccḍa n tsuqilt
WhatsApp Azen aseɣwen n usader ɣer uselkim-ik