Safety in Mines Research Advisory Committee Final Project Report The development of an occupational diseases database, to be managed by the Department of Minerals and Energy
Yüklə 0,49 Mb. Pdf görüntüsü
|
- Bu səhifədəki naviqasiya:
- Appendix 1 Design Specifications SIMRAC Project GEN 505
- Design Document Occupational Diseases Database 1 Introduction 1.1 System Overview Project Title
- 1.3 Definitions 1.3.1 Reportable Disease
- 1.3.2 Compensable Disease
- 2 Data Flow 2.1 Data Flow Diagram
- 2.2 Description of Data Flow
- 3 Functional Design 3.1 Functional Decomposition Diagram
- 3.2 Descriptions of Functions
- 4 Database Design 4.1 List of Tables LIST OF TABLES – OCCUPATIONAL DISEASES DATABASE
- LIST OF TABLES – OCCUPATIONAL DISEASES DATABASE
- 4.3 Attribute Definitions KEY
- 4.3.1 Shared SAMRASS Tables S1 – OCCUPATION
- 4.3.2 Personal Identification Tables D1 – PERSON
|
References Government Gazette No. 18260 of 5 September 1997. The Occupational Diseases in Mines and Works Act, No. 78 of 1973. The Compensation for Occupational Injuries and Diseases Act, No. 130 of 1993. Appendix 1 Design Specifications SIMRAC Project GEN 505 Occupational Diseases Database to be Managed by the Department of Minerals and Energy Design Specifications Table of Contents 1 Introduction...................................................................... 1 1.1 System Overview ...................................................................... 1 1.2 Design Approach....................................................................... 1 1.3 Definitions.................................................................................. 1 2 Data Flow ........................................................................ 2 2.1 Data Flow Diagram ................................................................... 2 2.2 Description of Data Flow ........................................................... 5 3 Functional Design............................................................ 5 3.1 Functional Decomposition Diagram .......................................... 5 3.2 Descriptions of Functions.......................................................... 9 4 Database Design ........................................................... 13 4.1 List of Tables ........................................................................... 13 4.2 Data Model .............................................................................. 14 4.3 Attribute Definitions ................................................................. 16 5 Data Input Forms (Paper) .............................................. 31 6 Data Input and Viewing Screens.................................... 34 7 Housekeeping Screens.................................................. 36 8 Ancillary Screens........................................................... 40 9 Standard Reports .......................................................... 47 9.1 Sample Reports....................................................................... 47 10 Interfaces ...................................................................... 52 10.1 Tables updated by the Import function ................................... 52 10.2 Transfer files – general ........................................................... 52 10.3 Transfer file record formats ..................................................... 53 10.4 Specifications for the Import function...................................... 60 11 System Requirements ................................................... 63 11.1 Data Storage ........................................................................... 63 A- 1
Occupational Diseases Database 1 Introduction 1.1 System Overview Project Title: The development of an occupational diseases database, to be managed by the Department Minerals and Energy, to record morbidity and mortality of occupational diseases in the South African mining industry. (Government Gazette No. 18260 of 5 September 1997). The system consists of a database and software to enter and view the data. The database maintains records of occupational diseases. It does not contain details of treatment, occu- pational hygiene data, or occupational medical surveillance records. The occupational disease records are stored against a personal record for each patient.
The software development will be done by the DME’s IT Section. The chosen database platform is Btrieve, and the Magic rapid application development tool will be used. The following assumptions have been made in the design: • A full relational database management system will be used; • The development environment is Windows-based. The database and software will be Year 2000 compliant; all dates will be stored and displayed in full “century” format. Security of programs and data will be maintained by the DME’s IT Section and user access control will be provided. The data is regarded as very sensitive, and so the DME’s IT Section will ensure that adequate protection is provided against “Hacking” (unauthorised access to the data, with or without malicious intent). 1.3 Definitions 1.3.1 Reportable Disease A Reportable Occupational Disease is a disease which, in terms of an Act of Parliament, such as the Occupational Diseases in Mines and Works Act, must be reported by an em-
A- 2 ployer to an official authority, such as the Department of Minerals and Energy. In the context of the Occupational Diseases Database, Reportable Disease refers to an actual occurrence of such a disease. 1.3.2 Compensable Disease A Compensable Occupational Disease is a Reportable Occupational Disease which results in a permanent disability for which compensation is paid. In the context of the Occupational Diseases Database, Compensable Disease refers to an occurrence of such permanent disability, for which compensation is actually paid.
See following page(s) (from page 3). A- 3
A- 4
A- 5
Reporting of diseases to the compensation bodies (at present, i.e. prior to implementation of the disease database) follows different routes as shown in the first page of the diagram (page 3). This depends on the Act under which the disease is covered. This situation is, however, changing. It is anticipated that the COID and ODMW Acts will be merged before the year 2000, and that the Mine Health and Safety Act will become more prominent as regulations are brought into force to define diseases under this Act. For the purposes of the Occupational Diseases Database, the employers (i.e. mines or mining houses) will usually report disease occurrences to the DME (see the second page of the diagram). The various compensation bodies will only need report to the DME in the case of a patient who is no longer in employment in the mining industry. As shown in the diagram, when a reportable or compensable disease is diagnosed, the mine will report this to the DME, for entry into the disease database, as well as sending in the claim to one of the statutory bodies for compensation. The mine will send an update to the DME if the disease is found to be compensable. 3 Functional Design 3.1 Functional Decomposition Diagram See following page(s) (from page 6). A- 6
A- 7
A- 8
A- 9
Functions are listed below. The numbering corresponds to that on the Functional Decomposition Diagram. Restricted functions are shown in square brackets. No facilities are provided in this system for maintaining the shared SAMRASS tables. For each code list, each of the shared SAMRASS tables and some other tables, a picklist will be needed; this will usually be a combo box. This is not specified below. The browsers, below, are opened from the main menu. The Add, Change and Delete options are selected from the corresponding browser. Every Delete option first asks for confirmation that the user really wants to delete the record before proceeding. Deletion of a record will not be permitted if this would violate referential integrity in the database. 1. Maintain Code Lists 1.1. Browse Diseases – screen form ScrCDi000. 1.1.1. Add Disease – screen form ScrCDi010. 1.1.2. Change Disease – screen form ScrCDi010. 1.1.3. [Delete Disease] 1.2.
Browse Disease Groups – screen form ScrCDG000. 1.2.1. [Add Disease Group] – screen form ScrCDG010. 1.2.2. Change Disease Group – screen form ScrCDG010. 1.2.3. [Delete Disease Group] 1.3. Browse Compensation Submission Result Types – screen form ScrCRT000. 1.3.1. Add Result Type – screen form ScrCRT010. 1.3.2. Change Result Type – screen form ScrCRT010. 1.3.3. [Delete Result Type] 1.4. Browse Compensation Submission Result Items – screen form ScrCRI000. 1.4.1. Add Result Item – screen form ScrCRI010. 1.4.2. Change Result Item – screen form ScrCRI010. 1.4.3. [Delete Result Item] 1.5. Browse Reporting Centres – screen form ScrCRC000. 1.5.1. Add Reporting Centre – screen form ScrCRC010. 1.5.2. Change Reporting Centre – screen form ScrCRC010. 1.5.3. [Delete Reporting Centre] 1.6.
Browse Types of Centre – screen form ScrCCT000. 1.6.1. Add Type of Centre – screen form ScrCCT010. 1.6.2. Change Type of Centre – screen form ScrCCT010. 1.6.3. [Delete Type of Centre] 2. Maintain User Rights 2.1. Browse Users – screen form ScrUse000. 2.1.1. [Add User] – screen form ScrUse010.
A- 10 2.1.2. [Change User Rights] – screen form ScrUse010. 2.1.3. [Delete User] 2.2.
Control User Login – screen form ScrUse100. 2.2.1. Validate User name and Password. At login, a user will enter his or her User name and Password. These will be compared with entries in the table, and access allowed or barred (with an error message). 2.2.2. Change Password. The login form will have two fields for entering a new password. If no entry is made in either field, then no change is made to the stored password for the user. Otherwise, the two fields are compared; if they are identical, the new password is stored in the table for the user. If there is a mismatch, a warning message is given, and login proceeds as if no attempt had been made to change the password. (The user can change it at the next login.) 3. Maintain Persons, including Personal Identification 3.1. Create Person record. This is only done through the Enter Occupational Disease function (see 4.4.2 – Enter Personal Details). The “Create Person” function merely creates a Person record from data supplied in the ScrDis120 screen form, and it may simply be implemented as an SQL statement. 3.2. Create Personal Identification. This is done through the Enter Occupational Disease function, and through the Find Person function (in Change mode). 3.3. Find Person – screen form ScrPer001. A browser is not provided, as there are likely to be many thousands of records, which could be unmanageable. This screen will be a pop-up serving other screens (e.g. ScrDis000); it will also be available as a maintenance screen, when opened from the main menu. 3.3.1. [Delete Person] – screen form ScrPer001. 3.3.2. [Change Person] – screen form ScrPer001. 4. Maintain Personal Disease Records 4.1. Browse Personal Disease Records – screen form ScrDis000. 4.2. Create Personal Disease Record. This function is called by another function (see the Logic Flow diagram, page 12), to create a new record.
4.3. Update Personal Disease Record. This function is called by another function (see the Logic Flow diagram, page 12), to update an existing record. 4.4. Enter Occupational Disease – screen form ScrDis100. If a tabbed form is used, this will be the Master form. Refer also to the diagram “Logic Flow for Disease Input”, (inserted, as page 12). 4.4.1. Enter Submitter & Employer Details – screen form ScrDis110. 4.4.2. Enter Personal Details – screen form ScrDis120. 4.4.3. Enter Disease Details (General) – screen form ScrDis130. 4.4.4. Enter Disease Details (Reportable) – screen form ScrDis130. 4.4.4.1. Enter NIHL Details – screen form ScrDis131. 4.4.4.2. Enter PNEU Details – screen form ScrDis132.
A- 11 4.4.4.3. Enter CRTB Details – screen form ScrDis133. 4.4.4.4.
Enter COAD Details – screen form ScrDis134. 4.4.4.5. Enter HEAT Details – screen form ScrDis135. 4.4.4.6. Enter OTHR Details – screen form ScrDis136. 4.4.5. Enter Disease Details (Compensation) – screen form ScrDis150. 4.4.6. Enter Occupational History. Calls the Occupational History Browser – screen form ScrHis000. 4.5.
Import Occupational Disease – this very complex function is specified in paragraph 10, on page 52. It provides for the import of data transferred from the mines, either electronically or on portable media, such as diskettes. (Data capture software for the mines is outside the project scope.) 5. Maintain Occupational History 5.1. Browse Occupational History – screen form ScrHis000. 5.1.1. Add Occupational History Record – screen form ScrHis000. 5.1.2. Change Occupational History Record – screen form ScrHis000. 6. Maintain Workforce Statistics 6.1. Browse Workforce Statistics – screen form ScrWrk000. 6.1.1. Add Annual Workforce Record – screen form ScrWrk000. 6.1.2. Change Annual Workforce Record – screen form ScrWrk000. 6.2.
Create Annual Workforce Record. This function is called by another function (see the Logic Flow diagram, page 12), to create a new record. 6.3.
Update Annual Workforce Record. This function is called by another function (see the Logic Flow diagram, page 12), to update an existing record.
A- 12
A- 13
4.1 List of Tables LIST OF TABLES – OCCUPATIONAL DISEASES DATABASE Tbl No Table Name Description Shared SAMRASS Tables S1 OCCUPATION Code list of Occupations of workpeople, as used by SAMRASS.
S2 MINES
Code list of Mines, as used by SAMRASS. S3 REGION-CODES Code list of Regions, as used by SAMRASS. S4 TECHNICAL MANAGER Code list of Owners of Mines, as used by SAMRASS. S5 MAIN COMMODITY Code list of Main Commodities produced by Mines, as used by SAMRASS. Occupational Diseases Database – Personal Identification Tables D1 PERSON Person table, containing details of each person (or patient), such as name and gender. D2 PERSONAL
IDENTIFICATION The Personal Identification table contains various identification numbers issued to a person, such as National ID, and passport number. Note that Company Number is kept in the Occupational History table.
D3 PERSONAL DISEASE RECORD Record of an official notification of an instance of an occupational disease. D4 OCCUPATIONAL HISTORY List of Occupations and employers (i.e. Mines) for which a person has worked. Includes employee’s Company Number. D5 ANNUAL
WORKFORCE Average number of people working on a mine in a reporting year. Used as a denominator in statistical calulations. Occupational Diseases Database – Code Lists, Diseases M1 DISEASE Code list of diseases. M2 DISEASE GROUP Code list of groups of diseases. Each Disease Group will have its own data input screen. Occupational Diseases Database – Code Lists, General C3 COMPENSATION SUBMISSION RESULT TYPE
Type of result from a submission for compensation. Results are given in different ways, e.g. percentage permanent disablement, or a degree of disablement. C4 COMPENSATION SUBMISSION RESULT ITEM
An entry in the list of possible results for a given type of result.
C5 REPORTING CENTRE The centre which reported the disease to the database. There will be some overlap between this and the Mines table.
A- 14
Tbl No Table Name Description C6 TYPE OF CENTRE Type of reporting centre. This may be a mine, or an official body such as a compensation commissioner. Occupational Diseases Database – System Tables A1 USER RIGHTS Controls access to the system, and user rights. 4.2 Data Model See following page(s) (page 15). A- 15
A- 16
KEY Code Meaning ** Primary key field + Foreign key field (+) Foreign key field, optional (i.e. may be null) DATA FORMAT Code Meaning LI, SI, TI Long, short, tiny integer. F Double precision floating point number. Cn Text string, n characters long. VCn Variable Text string, maximum n characters long. L Logical (Yes/No, or True/False). D Date and time. OLE OLE data, eg picture. A- 17
S1 – OCCUPATION Key Field Name Fmt Description ** Kode C4 SAMRASS Occupation code. Engelse-besk C50
Name of Occupation (English). Afrikaanse-besk C50 Name of Occupation (Afrikaans). Datum-onaktief D Date inactive. S2 – MINES Key Field Name Fmt Description ** MINE NUMBER SI Mine Code used by Minerals Bureau. 4 digits. NAME OF MINE C40 Name of Mine. + MAIN COMMODITY C2 Code for the main commodity being produced by a mine. + TECHNICAL OWNER C2 Code for the Owner (i.e. Technical Manager) of a mine. + REGION C1 Code for the administrative Region where a mine is located. MAXIMUM DEPTH SI UNDERGROUND L SURFACE
L OPENCAST
L AT SEA
L STATUS
C1 OPERATION C16 CHAMBER OF MINES L COMPETITION L SIMREC-STATUS C1 WORKS INDICATOR C1
** Code C2 SAMRASS code for the administrative Region where a mine is located. English-desc C50 Name of Region (English). Afrikaans-desc C50
Name of Region (Afrikaans). Date-inactive D Date inactive. A- 18
Key Field Name Fmt Description ** Code C2 SAMRASS code for the Owner of a mine. English-desc C50
Name of Owner (English). Afrikaans-desc C50 Name of Owner (Afrikaans). Date-inactive D Date inactive. S5 – MAIN COMMODITY Key Field Name Fmt Description ** Code C2 SAMRASS code for the main commodity being produced by a mine. English-desc C50 Name of Commodity (English). Afrikaans-desc C50
Name of Commodity (Afrikaans). Date-inactive D Date inactive. Notes: • SAMRASS Occupation and other codes are currently (mid-1998) being revised. • The SAMRASS code lists will continue to be maintained by the SAMRASS system, and will be accessed read-only by the Occupational Diseases System.
A- 19
D1 – PERSON Key Field Name Fmt Description ** PersonNumber LI A generated number used to link together records for the same person. Surname
C25 Person's family name. FirstNames C25
Person's first name, names or initials. Gender
C1 Valid values: (M) Male or (F) Female. DateOfBirth D Person's date of birth. DateOfDeath D Date the person died, whether as a result of an occupational disease, or not. May be null.
Notes: • PersonNumber is generated by the software. It is a simple sequential number. • When a new Personal Disease Record is created, the software will check whether a Person record already exists for the patient, by checking Personal Identification details, to try to avoid creating duplicate Person records. Yüklə 0,49 Mb. Dostları ilə paylaş:
|