M-Connect
John Pinder
Agenda
• Problems?
• Future development
• SQL server
• Oracle
• Web based
• Data dictionary
• Central repository
Problems
• Speed
• Robustness
• Maintenance
Problem Causes - Speed
• Source system data structure
^M("BARNES","FLORENCE","K",1381511376)
Surname
Forename
Middle Names
NHS Number
• Due to NHAIS user factors
Problem Causes - Speed
• Server workload
• Other applications
- SQL Server
- Oracle
- Exchange Server
Problem Causes - Speed
• Network traffic
• Applications competing for network resource
• Ophthalmic
• NHAIS ICM
• PCIS
• Open Exeter
Problem Causes - Robustness
• Orphaned licence processes
• Caused by cancelling queries in front end
• Licence record remains
• Limits amount of active connections available
Problem Causes - Maintenance
• Upgrade process
• Currently hard coded location
• Dependant on floppy drive
Problem Causes - Maintenance
•
•
•
•
Manual startup of M-Connect
Required on Cache reboot
Starts SQL0TCP process
SQL0TCP process not present – M-Connect
wont work
Re-development - SQL Server
•
•
•
•
Fast
Open
Robust
Scalability
Re-development - Oracle
•
•
•
•
Fast
Open
Robust
Scalability
Current system - Cache
•
•
•
•
Fast
Open
Robust
Scalability
System Redevelopment
•
•
•
•
•
•
SQL Server, Oracle and Cache all DBMS
All have similar functionality
Data structure problems remain
Server resource issues remain
Network resource issues remain
New upgrade issues
Problem Resolution - Speed
• Indexes
• e.g. R_PERSON_INDEX_NHS_NUMBER
• Used to link on NHS_NUMBER
• Provides all 4 fields
• Allows direct retrieval of records
• Other indexes for GP, Postcode, Date of Birth
• Local tables
• Using copies of data held locally
• Run “harvest” queries overnight
Problem Resolution - Robustness
• Orphaned licence records
• New routine
• Regular execution
• Automatic clear down
Problem Resolution - Maintenance
• New upgrade routine
• Prompt for upgrade file location
• Enables files to be copied anywhere
• New startup routine
• Runs on Cache reboot
• Automatic startup SQL0TCP
Data Dictionary
•
•
•
•
•
•
Currently Microsoft Access database
Requires update on each client PC
Migrate to single data dictionary
One copy of data dictionary to update
Ensure all users viewing latest version
Located where all users can view
• Web page
Central Repository
• Not widely used
• Needs promotion
• Regular submissions required
Conclusions
•
•
•
•
•
•
Redevelopment offers no improvement
User awareness and education
New upgrade routine
New startup routine
New licence cleardown routine
Data dictionary improvement