Medical Data Import (Generic) You can import the results of medical tests from laboratories or technical medical equipment to the SAP system as ASCII files.
The generic import is executed with the function module EHS00MDATAUPL_IMPORT independently of the examination category used.
This function is available for all examination category defined in the system.
During the generic import of medical test results, you can implement additional actions, such as carrying out conversions of examination results, with the BAdI
Import of Medical Data (Examination Results)
. Implementations of this BAdI are delivered with the standard system for the
audiogram
,
laboratory examination
, and
pulmonary
examination categories.
Importing medical data is done in the medical service component.
The data is available with space separators or tab separators in electronic form as ASCII files. You must specify the separator used in the Customizing activity
Specify Examination Categories
for the relevant examination category.
You have made all required setting in the Customizing activity
Specify Examination Categories
according to the settings described there for the relevant examination category.
To import data for the audiogram, laboratory examination, and pulmonary examination categories delivered with the standard system, the data must have the following structure:
Audiogram Examination Category
Field Name |
Type |
Length |
Format |
|
service_prov |
Char |
10 |
Key |
|
person_reference |
Char |
20 |
||
exam_code |
Char |
6 |
||
person |
Char |
25 |
Data |
|
short_name |
Char |
5 |
||
audio_baseline |
Char |
1 |
||
audio_machine |
Char |
20 |
||
audio_software |
Char |
20 |
||
exam_date |
Char |
8 |
yyyymmdd |
|
exam_time |
Char |
6 |
hhmmss |
|
db_left_125 |
Char |
13 |
||
db_right_125 |
Char |
13 |
||
db_left_250 |
Char |
13 |
||
db_right_250 |
Char |
13 |
||
db_left_500 |
Char |
13 |
||
db_right_500 |
Char |
13 |
||
db_left_1000 |
Char |
13 |
||
db_right_1000 |
Char |
13 |
||
db_left_2000 |
Char |
13 |
||
db_right_2000 |
Char |
13 |
||
db_left_3000 |
Char |
13 |
||
db_right_3000 |
Char |
13 |
||
db_left_4000 |
Char |
13 |
||
db_right_4000 |
Char |
13 |
||
db_left_6000 |
Char |
13 |
||
db_right_6000 |
Char |
13 |
||
db_left_8000 |
Char |
13 |
||
db_right_8000 |
Char |
13 |
||
uname |
Char |
12 |
||
aedtm |
Char |
8 |
yyyymmdd |
Laboratory Examination Category
Field Name |
Type |
Length |
Format |
|
service_prov |
Char |
10 |
Key |
|
person_reference |
Char |
20 |
||
exam_code |
Char |
6 |
||
test_no |
Char |
8 |
Data |
|
laboratory_patient |
Char |
10 |
||
patient_name |
Char |
50 |
||
exam_date |
Char |
8 |
yyyymmdd |
|
exam_time |
Char |
6 |
hhmmss |
|
reference_ext |
Char |
20 |
||
type_test |
Char |
60 |
||
result_value |
Char |
60 |
||
result_uom |
Char |
20 |
SAP unit of measurement |
|
result_reference_range |
Char |
60 |
||
result_normal_low |
Char |
7 |
||
result_normal_high |
Char |
7 |
||
result_abnormal_flag |
Char |
5 |
||
abnormality1 |
Char |
1 |
||
abnormality2 |
Char |
1 |
||
result_status |
Char |
1 |
||
uname |
Char |
12 |
||
aedtm |
Char |
8 |
yyyymmdd |
Pulmonary Examination Category
Field Name |
Type |
Length |
Format |
|
service_prov |
Char |
10 |
Key |
|
person_reference |
Char |
20 |
||
exam_code |
Char |
6 |
||
person |
Char |
25 |
Data |
|
pulmo_machine |
Char |
20 |
||
pulmo_software |
Char |
20 |
||
exam_date |
Char |
8 |
yyyymmdd |
|
exam_time |
Char |
6 |
hhmmss |
|
fev1_observed |
Char |
13 |
||
fev1_predicted |
Char |
13 |
||
fvc_observed |
Char |
13 |
||
fvc_predicted |
Char |
13 |
||
fev1_fvc_percent_obs |
Char |
13 |
||
fev1_fvc_percent_pred |
Char |
13 |
||
peak_flow |
Char |
13 |
||
vc |
Char |
22 |
||
uname |
Char |
12 |
||
aedtm |
Char |
8 |
yyyymmdd |
The characters for the first three fields,
service_prov
,
person_reference
, and
exam_code
, make up the key that is used to assign the data in the ASCII file to the corresponding object in the SAP system. To do this, the key field
person_reference
must be specified first. The entry in this field can be a medical service number, a personnel number, or a social insurance number. In the Customizing activity
Specify References for Importing Medical Data
for occupational health, you can specify for each examination category which of the three objects data should be assigned to.
See the following settings for customer-specific examination categories:
You must make all required entries in the Customizing activity
Specify Examination Categories
:
Specify the database table in which the imported examination results are saved.
The database table can contain more fields than the respective import structure.
Specify the table type that is used for processing imported medical examination results.
Specify the DDIC structure that maps one line in the file to import.
The descriptions of the structure components must match the field labels of the database table, because the import takes place using name equality.
The order of the structure components must match, however, the order of the fields in the file for the import, because they are imported in the defined order.
Specify the separator that is used in the file to import.
Importing from a space-delimited (separated by space) file:
The field lengths of the individual structure components must match the lengths used in the import file.
Importing from a tab-delimited (separated by tab) file:
The field lengths in the structure must match at least the field lengths in the file. In all other cases, the data will be truncated.
If additional fields are filled in the database table or if a data conversion before saving is required, you can implement the BAdI
Import of Medical Data (Examination Results)
accordingly.
The further you go into the medical service, the more restrictions you can impose on the number of data records that are imported.
With the BAdI
Import of Medical Data (Examination Results)
, you can fill further fields, carry out data conversions, and conduct checks, or implement additional functions after saving data.
You can display a log of successful and unsuccessful imports. The log is entered in the application log under the object EHS_OH_IM (EHS-OH: Import of Medical Data) or under the subobject EHS_OH_EXA (Import of Examination Results).
The corresponding examination category is saved as an external indication of the application log entry, for example, “01” for the import of audiogram data.