Installation guide

On Solaris, launch CLUI.
2.
Type select count(*) from map_event.
3.
On Windows, click Execute.
4.
Type select count(*) from map_event_audit.
5.
On Windows, click Execute.
Note:
The count(*) command returns a result with five decimal places.
If the tables are large (they could run to millions of records), you can optionally first export the data
to file by following the “Exporting auditing information to a file” procedure (topic number 9342)
in the IMPAX Server Knowledge Base. You can then trim the records by following other procedures
documented in the IMPAX Server Knowledge Base; notably, the “Defining when older audit records
are deleted from the database” topic (topic number 9345).
Verifying whether the database needs updates
for report migration
(Topic number: 60430)
4.
IMPAX 6.5.3 is able to store reports with links to multiple patient identifiers. These patient identifiers
come from Connectivity Manager, but are stored differently in IMPAX than in Connectivity Manager.
The domain_id in AgfaHC_Patient_ID is the same field as the Connectivity Manager field
issuer_of_patient_id. IMPAX requires that the combination of the patient_id and domain_id be
distinct values in AgfaHC_Patient_ID.
To support this, the Connectivity Manager issuer_of_patient_id file must be different for the Primary,
Alternate, and Global patient identifiers. This may require updates to the Connectivity Manager
database and mappings and to the AgfaHC_patient_id table.
Changes to these fields are most easily done before the report data migration. These changes prevent
the Application Server from hanging after receiving new reports for inserting into the AgfaHC tables.
To verify whether the database needs updates for report migration
1. On the Connectivity Manager, in Query Analyzer, run the following queries:
a.
use mcf
b.
select distinct use_of_patient_id from mcf_patient_id
c.
select distinct issuer_of_patient_id from mcf_patient_id
2. If either of these queries gets more than one response, this may indicate a problem. To resolve
it, work with the Connectivity Manager integrator and Agfa support.
It is much easier to resolve any data issues before migrating reports to IMPAX.
AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3,or WEB1000 to IMPAX 6.5.3 104
Agfa Company Confidential—Subject to Non-Disclosure Obligation