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ü
|
|
C6 – TYPE OF CENTRE Key Field Name Fmt Description ** RepCentreTypeCode C2 Code for type of reporting centre. RepCentreType C40
Name of type of reporting centre. IsCompCom L Is this type of reporting centre an official body? See note, below. Notes: • The IsCompCom flag controls which centres can issue official case numbers for disease occurrences. (See CCRefNo and CCCentreCode in the Personal Disease Record table.) • The initial records in the table are given below. A- 30
Name IsCompCom CC Compensation Commissioner Y AC Compensation Assurance Co. Y MI Mine N MH Mining House N 4.3.6 System Tables A1 – USER RIGHTS Key Field Name Fmt Description ** UserName C6 Login name for user. NameOfUser C40
Name of person using this login name. Password
C6 Login password for user. AccessLevel TI Authorisation level for user. See note below. Notes: • The AccessLevel will be used by the software to ensure that users only perform authorised functions in the system. Valid values are given in the following table. AccessLevel Comment 1 System rights – can perform any function that the system provides. 2 May create, read, update and delete. 3 May create, read and update. 4 Read access only. • Some discussion will be needed, to decide on the rights which are to be assigned to the different AccessLevels.
A- 31
List of Forms Reference Description FrmDis000 Disease Input Form
• The Disease Input Form contains the full details of a disease occurrence, including the compensation details. It is anticipated that mines may submit disease occurrence data in two stages: first the “reportable” data, then, after the results of the compensation submission (if any) have been returned, the “compensation” data. • A copy of the form GW 24/56 (Summary of Complete Labour History), which is sent to the MBOD, must also be attached to the Disease Input Form.
For examples of input forms, see following page(s) (from page 32). A- 32
Occupational Disease Input Form (Form: FrmDis000) DME 90 (1) Organisation Submitting Data & Current Employer of Patient Current or SAMRASS Previous Employer: Mine Code: Submitted by: Code: (e.g. Employer, as above, or MBOD) Employer’s Workforce: Year:
(Enter numbers below, for previous calendar year) Surface:
U/ground: Risk:
O/Cast: At Sea:
Total: ( Ensure that Surface + U/ground + O/Cast + At Sea = Total) Submitter’s Case No:
SA National ID: Passport No: Industry No: PF Number: TEBA No:
Coy No: Surname:
First Names: Date of Birth: / /
/ / dd mm yyyy
dd mm yyyy Gender: M [ ]
F [ ] (3) Details of Disease (General) Date Examined: / /
(or Diagnosed) dd mm yyyy Disease Group: NIHL [ ] PNEU [ ] CRTB [ ] COAD [ ] HEAT [ ] OTHR [ ] Disease: Disease Code: (e.g. Silicosis) (per DME’s list) Person who Completed this Form (Not for data input) Name: Telephone No: Date: / / A- 33 (Form: FrmDis000) DME 90 (4) Details of Disease (Reportable Stage) (i) NIHL – Noise Induced Hearing Loss 0.5
1 2 3 4 6 8 kHz > 15 dB loss in 12 months: > 20 dB loss in 20 months: (Mark with a cross “X” if applicable) (ii) PNEU – Pneumoconioses Chest X-Ray ILO Classification: e.g. p 1/1
Compensation Submission on Diagnosis: TB current NCD
1º 2º
COAD – Chronic Obstructive Airways Disease FEV1 Deterioration: (Mark with a cross “X” if applicable) FVC Deterioration: FEV1/FVC Deterioration:
Heat Exhaustion: (Off work for > 48 hrs) OR Heat Stroke: (Hospital diagnosis) (vi) OTHR – Other Occupational Diseases Reason:
(5) Details of Disease (Compensation Submission) Severity Index NIHL – Average Hearing Loss: dB (0.5; 1; 2; 3 kHz) General:
Date Submitted: / / Date Returned: / / dd mm yyyy dd mm yyyy Compensation Result: e.g. % PD; NCD; 1º; 2º Disease Caused Death: (Mark with a cross “X” if applicable) Employment Status Changed: Date Status Changed: / /
Which CC?: (Compensation Commissioner, MBOD or RMA) Have you attached a copy of form GW 24/56 (Summary of Complete Labour History)?
A- 34
List of Screens for Data Input Reference Description ScrDis000 Browse Personal Disease Records ScrDis100 (Master form) Personal Disease Record Input Screen ScrDis110 Submitter & Current Employer ScrDis120 Personal Details of Patient ScrDis130 Details of Disease ScrDis131 (Subform) Reason Reportable – NIHL ScrDis132 (Subform) Reason Reportable – Pneumoconioses ScrDis133 (Subform) Reason Reportable – CRTB ScrDis134 (Subform) Reason Reportable – COAD ScrDis135 (Subform) Reason Reportable – Heat-related Ilness ScrDis136 (Subform) Reason Reportable – Other Occupational Disease ScrDis150 Details of Disease (Compensation Submission) ScrHis000 Browse Occupational History Records, including Add/Change. ScrWrk000 Browse Workforce Statistics, including Add/Change. Key to field types: Type Meaning R Read-only B Button
W Writeable text field C Code-list (combo box) X Check box (Yes/No) S Spin control M Mandatory data Screen: ScrDis000 – Browse Personal Disease Records (D3) Label Field Type Notes Patient
D1.Surname + D1. FirstNames R Header above browser, showing name of patient whose records are being viewed. Date DiseaseName R Disease
DiseaseCode + C1. DiseaseName R
A- 35
Field Type Notes Compens-
able IsCompensable R Interpret code as shown in the data definition. [Find]
B Finds a Person record, using form ScrPer001. [New]
B Opens ScrDis100 (or, perhaps, ScrDis110). [Add]
B Opens ScrDis100 (or, perhaps, ScrDis110). [Change]
B Opens ScrDis100 (or, perhaps, ScrDis110). [Close]
B • Refer to the sample screen layout for this form, and to notes on the sample screen. Screen: ScrDis100 – Personal Disease Record Input Screen (D3) If used, this will be a Master Form, containing as tabbed forms, ScrDis110, ScrDis120, ScrDis130 and ScrDis150. The contents of this screen form will need to be discussed. Screen: ScrDis110 – Submitter & Current Employer • Refer to the sample screen layout for this form. Screen: ScrDis120 – Personal Details of Patient • Refer to the sample screen layout for this form. Screen: ScrDis130 – Details of Disease • Refer to the sample screen layout for this form. Screen: ScrDis131 – Reason Reportable – NIHL Screen: ScrDis132 – Reason Reportable – Pneumoconioses Screen: ScrDis133 – Reason Reportable – CRTB Screen: ScrDis134 – Reason Reportable – COAD Screen: ScrDis135 – Reason Reportable - Heat-related Ilness Screen: ScrDis136 – Reason Reportable - Other Occupational Disease • These are Subforms for ScrDis130; refer to the sample screen layout. Screen: ScrDis150 – Details of Disease (Compensation Submission) • Refer to the sample screen layout for this form. Screen: ScrHis000 – Browse Occupational History Records, including Add/Change (D4) • Refer to the sample screen layout for this form. A- 36
• Refer to the sample screen layout for this form. 7 Housekeeping Screens List of Screens for Housekeeping Reference Description ScrCDi000 Browse Diseases ScrCDi010 Add/Change Disease ScrCDG000 Browse Disease Groups ScrCDG010 Add/Change Disease Group ScrCRT000 Browse Compensation Submission Result Types ScrCRT010 Add/Change Compensation Submission Result Type ScrCRI000 Browse Compensation Submission Result Items ScrCRI010 Add/Change Compensation Submission Result Item ScrCRC000 Browse Reporting Centres ScrCRC010 Add/Change Reporting Centre ScrCCT000 Browse Type Of Centres ScrCCT010 Add/Change Type Of Centre
Code
DiseaseCode R Name DiseaseName R Group DiseaseGroupCode R [Add] B Opens ScrCDi010. [Change] B Opens ScrCDi010. [Delete] B [Close] B Screen: ScrCDi010 – Add/Change Disease (M1) Label Field Type Notes Code
DiseaseCode MW/R
May not be updated in Change screen.
Name DiseaseName MW Definition DiseaseDefinition W Group DiseaseGroupCode MC Picklist from Disease Group table. Governing Act
GoverningAct W
A- 37
Field Type Notes Other
Regulations OtherRegulations W Notification Rules NotifyRules W Compensa- bility Rules CompensRules W Notes on
Disease NotesOnDisease W Date
Meaning DateMeaning MC See data definition for valid values. ResultType ResultTypeCode MC Picklist from Compensation Submission Result Type table. [Accept]
B Save changes, close form. [Cancel] B Reject changes, close form. Screen: ScrCDG000 – Browse Disease Groups (M2) Label Field Type Notes Code
DiseaseGroupCode R Name DiseaseGroupName R Maximum % PD MaxPPD
R [Add]
B Opens ScrCDG010. [Change] B Opens ScrCDG010. [Delete] B [Close] B Screen: ScrCDG010 – Add/Change Disease Group (M2) Label Field Type Notes Code
DiseaseGroupCode MW/R
May not be updated in Change screen.
Name DiseaseGroupName MW Maximum
% PD MaxPPD
MW Can Cause Death CanCauseDeath MX [Accept]
B Save changes, close form. [Cancel] B Reject changes, close form. A- 38
Label Field Type Notes Code
ResultTypeCode R Name ResultTypeName R Data Type ResultDataType R [Add] B Opens ScrCRT010. [Change] B Opens ScrCRT010. [Delete] B [Close] B Screen: ScrCRT010 – Add/Change Compensation Submission Result Type (C3) Label Field Type Notes Code
ResultTypeCode MW/R
May not be updated in Change screen.
Name ResultTypeName MW Data Type ResultDataType MC See data definition for valid values. [Accept] B Save changes, close form. [Cancel] B Reject changes, close form. Screen: ScrCRI000 – Browse Compensation Submission Result Items (C4) Label Field Type Notes Result Type ResultTypeCode R C3.ResultTypeName might be preferable. Name
ResultName R Stage ResultStageCode R [Add] B Opens ScrCRI010. [Change] B Opens ScrCRI010. [Delete] B [Close] B Screen: ScrCRI010 – Add/Change Compensation Submission Result Item (C4) Label Field Type Notes Result Type ResultTypeCode MC/R
Picklist from Compensation Submission Result Type table. May not be updated in Change screen. Code
ResultCode MW/R
May not be updated in Change screen.
Name ResultName MW Stage
ResultStageCode MC See data definition for valid values. Nominal % PD
NominalPPD W
A- 39
Field Type Notes Upper
% PD UpperPPD
W [Accept]
B Save changes, close form. [Cancel] B Reject changes, close form. Screen: ScrCRC000 – Browse Reporting Centres (C5) Label Field Type Notes Code
RepCentreCode R Name RepCentreName R [Add] B Opens ScrCRC010. [Change] B Opens ScrCRC010. [Delete] B [Close] B Screen: ScrCRC010 – Add/Change Reporting Centre (C5) Label Field Type Notes Code
RepCentreCode MW/R
May not be updated in Change screen.
Name RepCentreName MW Centre
Type RepCentreTypeCod e MC
Comment Comment
W [Accept]
B Save changes, close form. [Cancel] B Reject changes, close form. Screen: ScrCCT000 – Browse Type Of Centres (C6) Label Field Type Notes Code
RepCentreTypeCod e R Type RepCentreType R [Add]
B Opens ScrCCT010. [Change] B Opens ScrCCT010. [Delete] B [Close] B Screen: ScrCCT010 – Add/Change Type Of Centre (C6) Label Field Type Notes Code
RepCentreTypeCod e MW/R May not be updated in Change screen.
Type RepCentreType MW
A- 40
Field Type Notes Is Compen- sation Com- missioner? IsCompCom MX The label may need to be abbreviated. [Accept]
B Save changes, close form. [Cancel] B Reject changes, close form. 8 Ancillary Screens List of Ancillary Screens Reference Description ScrPer001 Find Person. Also allows some maintenance. ScrUse000 Browse Users ScrUse010 Add User/Change User Rights ScrUse100 Control User Login
• Refer to the sample screen layout for this form. Screen: ScrUse000 – Browse Users (A1) Label Field Type Notes UserName
UserName R Name of User NameOfUser R Access
Level AccessLevel R [Add]
B Opens ScrUse010. [Change] B Opens ScrUse010. [Delete] B [Close] B Screen: ScrUse010 – Add User/Change User Rights (A1) Label Field Type Notes UserName
UserName MW/R
May not be updated in Change screen.
Name of User
NameOfUser MW Password Password MW Access Level AccessLevel MS See data definition for valid values. A- 41
Field Type Notes [Accept]
B Save changes, close form. [Cancel] B Reject changes, close form. Screen: ScrUse100 – Control User Login Label Field Type Notes UserName
UserName MW Does not update record in table. Password Password
MW Does not update record in table. New Password
(Password) W Only update record in table if New Password is entered and is identical with Repeat New Password. Repeat
New Password
(Password) W [Accept] B Save changes, close form. [Cancel] B Reject changes, close form. For examples of sample screen layouts, see following page(s) (from page 42). A- 42
A- 43
A- 44
A- 45
A- 46
A- 47
List of Reports Reference Description RptPer001 Person Details RptDis001 Disease Occurrence Details RptDis002 Disease List for Person RptDis003 Monthly Disease Report RptDis011 Disease Classification by #a# (parameter to be defined) RptDis012 Disease Classification by #b# (parameter to be defined) RptDis013 Disease Classification by #c# (parameter to be defined) RptDis014 Disease Classification by #d# (parameter to be defined) RptDis015 Disease Classification by #e# (parameter to be defined) RptDis016 Disease Classification by #f# (parameter to be defined) RptDis017 Disease Classification by #g# (parameter to be defined) RptDis018 Disease Classification by #h# (parameter to be defined) RptDis019 Disease Classification by #i# (parameter to be defined)
See following page(s) (from page 48). A- 48
Person Details Person Number: 000101234 Surname:
Bloggs First Names: Joseph Alfred Gender:
M Date of Birth: 12 Dec 1949 Date of Death: N/A SA National ID: 49121251230001 Passport: 45M11220099 Industry Number: 111222 PF Number: 333444 TEBA Number: (none)
From
To Mine
Occupation Employee ID 01 Jan 1972
13 Sep 1997
Vaal Reefs Boiler Maker AA123456 02 Jan
1970 31 Dec
1971 Vaal Reefs Boiler Maker Aide AA123456
A- 49
Person Details Person Number: 000101234 Surname:
Bloggs First Names: Joseph Alfred Gender:
M Date of Birth: 12 Dec 1949 Date of Death: N/A SA National ID: 49121251230001 Passport: 45M11220099 Industry Number: 111222 PF Number: 333444 TEBA Number: (none)
Current Employer: Code: Submitted by: Code: Submitter’s Case No:
Date Examined: / /
(or Diagnosed) Disease Group: NIHL [ ]
PNEU [ ]
CRTB [ ]
COAD [ ]
HEAT [ ]
OTHR [ ]
Disease: DiseaseCode: Reportable? Reason:
Compensable Details General:
Date Submitted: / / Date Returned: / / Compensation Result: Disease Caused Death: Employment Status Changed: Date:
/ / Note (reason): CC Case No: Comp’n Comm: A- 50
Person Details Person Number: 000101234 Surname:
Bloggs First Names: Joseph Alfred Gender:
M Date of Birth: 12 Dec 1949 Date of Death: N/A SA National ID: 49121251230001 Passport: 45M11220099 Industry Number: 111222 PF Number: 333444 TEBA Number: (none)
Date
Disease Compensable Sub. Case No CC Case No 13 Sep 1997
Noise Induced Hearing Loss Y 0123456789 01A5597 20 May
1988 Silicosis Y 0012345678 01A4488 A- 51
Occupational Diseases Reported during the Month Disease
Reportable Compensable Total Noise Induced Hearing Loss 1234 112
1234 Total for Group: NIHL 1234 112
1234 Silicosis 512 23
Asbestosis 12 3 12 Total for Group: PNEU 524 26
… … … … Note: • The contents of this proposed report, and the method of deriving the figures on it, will be decided by the DME. A- 52
This section deals with the electronic transfer of occupational disease data from the mines and other organisations (“Submitters”) into the Occupational Diseases Database. The Submitter creates a transfer file, and sends this to the DME, either on removable media such as diskette or CD, or by e-mail, or over a network. The DME then imports this data into the tables of the Occupational Diseases Database.
The database tables which will be updated by the Import function are: Tbl No Table Name D1 Person D2 Personal Identification D3 Personal Disease Record D4 Occupational History D5 Annual Workforce As will be seen in the following paragraph, the different kinds of transfer file record provide the data needed by these tables. 10.2 Transfer files – general There is a single type of transfer file containing different types of record (or line), delimited by the CR-LF pair. The maximum length of a record is 256 characters. The file is in ascii format; no non-printable characters are permitted. If files are being transmitted over public networks where there is a risk of “hacking,” encryption may be used; however this is outside the scope of the current research project. The filename consists of exactly 4 characters representing the Submitter’s RepCentre- Code, padded with trailing underscores if necessary, followed by a four-digit sequential number generated by the Submitter, padded with leading zeroes if necessary. The filename extension is “.ODD” (an abbreviation of “Occupational Disease Data”). The sequential numbers may eventually be re-used; but as this is unlikely to happen within quite a few years, and files will be deleted after use, it should not cause a problem. A- 53 A single transfer file will generally contain occupational disease records for many patients. It is anticipated that a mine will transmit a transfer file each month or week, depending on data volumes. The general order of the records (excluding dummy records) in a transfer file would be as in the following table. The record types are described in the next paragraph. Indenting in the table shows a hierarchy, e.g. one or more Employers per Submitter, one or more Personal records per Employer. Transfer File: Overall Structure Record Type Comments Submitter Exactly one Submitter record per file. Employer
At least one Employer record per file. Personal
One or more Person records per Employer. Disease
One or more Disease records per Person. Optional. … History One or more History records per Person. Optional. … Personal Next Person. Disease
History … Employer Next Employer. …
With the exception of dummy records, each record is fixed-format. There are 6 different record types which may appear in the transfer file, identified by a 2- character prefix, as shown in the following table. Record lengths exclude the terminators.
Dummy
X0, X1, …
X9 varies,
min. 2, max
256 This type of record may appear anywhere in the file. The originator may use it for comments, or for control or readability purposes. It is ignored by the system. Submitter S1 6 The organisation submitting the data. Employer E1 70 The patient or patients’ most recent employer, and workforce data. A- 54
Record Type Prefix Length Contents Personal
P1 174
Personal identification details of the patient. Disease
D1 130
Occupational disease details of the patient. History
H1 46 Occupational history details of the patient. The following table lists the various data types used in fields in the transfer file. Transfer File: Data Types Code Format Description C Character Any printable ascii character, or as limited by the data itself (i.e. the field in the table into which the data will be copied). N Numeric A valid number, as an ascii character string taken from the digits 0 to 9. If the data itself permits, there may be a decimal point, and/or a leading minus sign. D Date
The date format is numeric, yyyymmdd, for example “19530531”. L Logical
A single character, “Y” or “N”, representing True or False respectively. In every case except the Dummy record, if there is no data to be put in a field, the field must be filled with blanks, e.g. if a patient is still alive, the DateOfDeath will contain 8 spaces. Field names in the transfer file are the same as the field names in the database tables into which the data will be put. Transfer File Record: Dummy Target Table: None Field Name Lengt h Data Type Contents Prefix
2 C “X0”, or “X1”, or … “X9” Comment < 254 C Anything the originator wishes to record. Total. 2 < length < 256
A- 55
Target Table: D3 – Personal Disease Record Field Name Lengt h Data Type Contents Prefix
2 C “S1” VersionNo 2 N File format version number. Currently 1. RepCentreCod e 4
“Submitted by” – code for the centre which reported the disease to the database. Total. 8
• There will be only one Submitter Data record in a file, and it will be the first non-dummy record. • The RepCentreCode is mandatory; it will not be written to a Personal Disease Record immediately, but will be kept in memory and written to each Personal Disease Record created or updated. This should be the same as the first 4 characters of the filename. • In the import function used by the DME in the database system, VersionNo will be incremented if changes are made to the transfer file format. How- ever, Submitters may not be able to implement changes simultaneously with the DME, so this field will allow older file formats to be handled during a transitional period. It is suggested that the DME keep the file format VersionNo in sync with the program version number.
Prefix
2 C “E2” MineCode 4 N Mine Code (integer) used by Minerals Bureau.
YearNo 4 N Number of year for records, eg 1998. NoOfWorkers 10 N
year. NoOfSfc
Workers 10 N Total number of surface workers on the mine for the year. NoOfUgWorkers 10 N Total number of underground workers on the mine for the year. NoOfOC Workers
10 N Total number of open-cast workers on the mine for the year. NoOfSea
Workers 10 N Total number of at-sea workers on the mine for the year. A- 56
Target Table: D3 – Personal Disease Record; D5 – Annual Workforce Field Name Length Data Type Contents NoOfRisk
Workers 10 N Total number of health risk workers on the mine for the year. Health risk workers are those persons working on the mine who have periodic medical surveillance examinations, regardless of where they work.
Total. 70
• There will usually be only one Current Employer Data record in a file, and it will follow the Submitter record. If, however, the Submitter is RMA or a Compensation Commissioner, there could be several Current Employer Data records. • The Current Employer Data record relates to all Personal Data records and Personal Disease Data records after it, until another Current Employer Data record is found. • The MineCode is mandatory; it will not be written to a Personal Disease Record immediately, but will be kept in memory and written to each Personal Disease Record created or updated after it. Transfer File Record: Personal Data Target Tables: D2 – Personal Identification; D1 – Person Field Name Length Data Type Contents Prefix
2 C “P1” IDTypeCode(1) 1 C “N” IDNumber(1) 20 C
IDTypeCode(2) 1 C “T” IDNumber(2) 20 C
IDTypeCode(3) 1 C “I” IDNumber(3) 20 C
IDTypeCode(4) 1 C “F” IDNumber(4) 20 C
IDTypeCode(5) 1 C “P” IDNumber(5) 20 C
Surname 25 C Person's family name. FirstNames 25 C
Gender 1 C Person's gender: (M) Male or (F) Female. DateOfBirth 8 D
DateOfDeath 8 D Person's Date of Death. Total. 174
A- 57
• The IDTypeCodes must be given (and in uppercase) as they will be used in the import function for locating records. • As stated above, this is a fixed-format record. If there is no entry for a given IDNumber, its position must be filled with spaces. The order of the IDNumbers may not be changed. At least one IDNumber must be supplied. Transfer File Record: Personal Disease Data Target Table: D3 – Personal Disease Record Field Name Length Data Type Contents Prefix
2 C “D1” DiseaseCode 4 C National code for disease. EntryDate 8 N
PreviousEntry Date
8 D Previous date examined or diagnosed for this disease, if any. MineRefNo 10 C
for this disease occurrence. CCCentreCode 4 C
that issued the CCRefNo. CCRefNo
10 C MBOD, RMA or CC’s case number for this disease occurrence. EmployeeID 16 C
available. MonthsInMining 2 N
working in the mining industry when the disease was diagnosed. Notifiable Reason
16 C Why Notifiable. Used in various ways; see note below. SubmittedToCC 1 L
hearing. DateSubmitted 8 D
Blank if SubmittedToCC is False. DateReturned 8 D
hearing. IsCompensable 1 C
(Y) Yes, (N) No and (U) Undecided. ResultCode 3 C
submission. Compensable Reason 16
Why Compensable. Used in various ways; see Note, below. Compensable PPD
3 N Result of Compensation hearing, giving severity as a percentage permanent disablement. Default zero. See note below. A- 58
Target Table: D3 – Personal Disease Record Field Name Length Data Type Contents DiseaseCaused Death 1
Whether the patient died as a result of the disease. Possible values are: (Y) Yes, (N) No and (U) Undecided (meaning that the patient died, but the cause has not yet been determined). EmployStatus Changed 1
Whether the patient had to change employment permanently as a result of the disease. DateEmploy Changed 8
Date the patient had to change employment as a result of the disease. May be empty. Total. 130
Notes: • Mandatory fields: DiseaseCode, EntryDate, MonthsInMining, Notifiable Reason. • A Personal Disease Data record will be for the Person referred to in the nearest previous Personal Data record in the file. • The MineCode is implied (i.e. remembered) from the Current Employer Data record. • The RepCentreCode is implied (i.e. remembered) from the Submitter Data record. • IsNotifiable will be set to True for each Personal Disease Data record in the file. • The NotifiableReason is used in different ways. These are given in the notes under the specifications for the database table: Personal Disease Record.
• The CompensableReason is used in different ways. These are given in the notes under the specifications for the database table: Personal Disease Record.
• ResultTypeCode is copied from the applicable Disease record when the Personal Disease Record is created. • The CompensablePPD is used in different ways. These are given in the notes under the specifications for the database table: Personal Disease Record.
Transfer File Record: Occupational History Data Target Table: D5 – Occupational History Field Name Length Data Type Contents Prefix
2 C “H1” MineCode 4 N Mine Code used by Minerals Bureau. SamOccupation ID 6
SAMRASS Occupation code. A- 59
Target Table: D5 – Occupational History Field Name Length Data Type Contents DateFrom
8 D The date on which this period of employment started. DateTo
8 D The date on which this period of employment ended. See note below. EmployeeID 16 C
available. Terminated 1 L
employer on DateTo. This is usually only of significance for the last record of a series, to show whether the employee was still in service after the date of diagnosis. Reliability 1 C Code for the perceived reliability of this record: (C) Confirmed; (U) Unconfirmed. Total. 46
• An Occupational History Data record will be for the Person referred to in the nearest previous Personal Data record in the file. • For the current employer (if any), DateTo must be ≥ EntryDate (i.e. date examined or diagnosed), and Terminated will be False. • A “Confirmed” Reliability would typically be used for an employer’s own records of the employee’s service. Details of previous employment would be regarded as “Unconfirmed”, unless documentary evidence has been produced to the current employer (or Submitter).
A- 60
This is a description of function 4.5, Import Occupational Disease, on page 11. The notes in the preceding paragraphs should also be referred to. If a fatal error is encountered, the function will give an error message before aborting. If any non-fatal errors are encountered an error (or warning) message is given, and the program continues executing. These error messages appear both on the screen and in an error report. The same validity tests as for manual data entry must be applied, for example, a key field may not be blank. These are not all specifically mentioned below. There is a processing flag, ValidPerson, which stops Disease and History data being entered against the wrong Person. The import function will skip any Dummy records encountered in the transfer file, without processing them. They are therefore ignored in the following steps. Step 1. Read the first line (i.e. non-Dummy record) from the file. If it is not the Submitter Data record, abort. If the VersionNo is invalid, abort. Invoke the file reading routines for the VersionNo. If the “Submitted by” RepCentreCode is invalid, abort. (See table C5 – Reporting Centre; it should also agree with the file name). Store the RepCentreCode in a memory variable for subsequent use. Go to the next Step. Step 2. Read the next line from the file. If it is not a Current Employer Data record, abort. Go to the next Step. Step 3. If MineCode is invalid (see table S2 – Mines), abort. Store MineCode in a memory variable for subsequent use. If YearNo is blank, go to the next Step. If YearNo is not a valid year, give a warning message and go to the next Step. If any of the following fields is non-blank and a valid number, write it to table D5 – Annual Workforce: NoOfSfcWorkers, NoOfUgWorkers, NoOfOCWorkers and NoOfSeaWorkers. The sum of these fields should be equal to NoOfWorkers; if not, give a warning message. Write the calculated value of NoOfWorkers to the table. If NoOfRiskWorkers is non-blank, write it to the table. Go to the next Step. Step 4. Read the next line from the file. If at end-of-file, exit. If the line is a Personal Data record, go to the next Step. If the line is a Personal Disease Data record: A- 61 If ValidPerson is True, go to Step 8. Otherwise, repeat this Step. If the line is an Occupational History Data record: If ValidPerson is True, go to Step 11. Otherwise, repeat this Step. If the line is a Current Employer Data record, go to Step 3. Otherwise: Give a warning message (it is an invalid record), Repeat this Step. Step 5. Handle a Personal Data record from the file, as follows. First try to locate an existing record for this Person in table D2 – Personal Identification: Set ValidPerson to True. For n=1 to 5 If IDNumber(n) is non-blank: If IDTypeCode(n) is invalid, give a warning message and skip to the “Next n”. If IDTypeCode(n) = “N”: Search for a Personal Identification record whose IDTypeCode = IDTypeCode(n) and Left (IDNumber, 10) = Left (IDNumber(n), 10). Notes:
§ Left() is a substring function which returns the first portion of the input string, 10 characters in this case. § The last 3 digits of a National ID can change. Otherwise: Search for a Personal Identification record whose IDTypeCode = IDTypeCode(n) and IDNumber = IDNumber(n). If a matching record is found: In a memory variable, store the PersonNumber from the located record in table D2 – Personal Identification. Go to the next Step. Next n
If all of the IDNumbers(n) were blank: Set ValidPerson to False, Give a warning message, Go to Step 4. If no matching record was found, go to Step 7. Step 6. Handle an existing Personal Data record in the database, as follows. Update the table D1 – Person: Locate the corresponding record for the PersonNumber in the table. For each of the following fields in the file record, if the field is non- blank, update the field in the table record: Surname, FirstNames, Gender, DateOfBirth, DateOfDeath. Update the table D2 – Personal Identification: Locate all the records for the PersonNumber in the table. For n=1 to 5 If IDNumber(n) is non-blank: If the matching table record exists: If IDTypeCode(n) = “N” Update IDNumber in the table record. A- 62 Note: § A National ID can change. Otherwise: Create a new record in the Personal Identi- fication table for the PersonNumber (memory variable), IDTypeCode(n) and IDNumber(n). Next n Go to Step 4. Step 7. Insert a new Personal Data record in the database, as follows. In a memory variable, allocate a new PersonNumber. Create the new record in the Person table, using the new PersonNumber, and those fields from the file which were non-blank: Surname, FirstNames, Gender, DateOfBirth, DateOfDeath. Create a new record in the Personal Identification table for each valid IDTypeCode(n) from the file record, where IDNumber(n) is non-blank. Go to Step 4. Step 8. Handle a Personal Disease Data record from the file, as follows. If if any of the following fields in the file record is blank, give a warning mes- sage and go to Step 4: DiseaseCode, EntryDate, MonthsInMining, NotifiableReason. For the current PersonNumber (memory variable), DiseaseCode and EntryDate, search for a record in the D3 – Personal Disease Record table. If a record is found, go to the next Step, otherwise go to Step 10. Step 9. Handle an existing Personal Disease Data record in the database, as follows. Update the table record with any of the following non-blank fields from the file record: PreviousEntryDate, MineRefNo, CCCentreCode, CCRefNo, EmployeeID, MonthsInMining, NotifiableReason, SubmittedToCC, DateSubmitted, DateReturned, IsCompensable, CompensableReason, ResultCode, CompensablePPD, DiseaseCausedDeath, Employ- StatusChanged, DateEmployChanged. Go to Step 4. Step 10. Insert a new Personal Disease Data record in the database, using the memory variables for PersonNumber, RepCentreCode and MineCode, and the non-blank fields in the record read in from the file. Use suitable defaults for the blank fields. Go to Step 4. Step 11. Handle an Occupational History Data record from the file, as follows. If the record contains any blank fields other than EmployeeID, give a warning message and go to Step 4. For the current PersonNumber (memory variable), MineCode, SamOccupationID and DateFrom, search for a record in the D5 – Occupational History table. If a record is found, go to the next Step, otherwise go to Step 13. Step 12. Handle an existing Occupational History Data record in the database, as follows.
Update DateTo, EmployeeID (if non-blank), Terminated and Reliability in the table record. Go to Step 4.
A- 63 Step 13. Insert a new Occupational History Data record in the database, using the memory variables for PersonNumber, and the fields in the record read in from the file. Go to Step 4.
Basic installation 300 Mbytes (suggested). Person
Allow 350 bytes per Person record. This makes an allowance for Occupational History, also. Disease Allow 150 bytes per Disease record. Yüklə 0,49 Mb. Dostları ilə paylaş:
|