(warning)     (warning)     (warning)     (warning)

The new wiki link for this data flow is here:

Technical documentation - MEDEXIS Report

Please update the doc there and no longer here.

(warning)    (warning)       (warning)       (warning)


General presentation

Objective of the application

 

MEDEXIS = MEDical EXposure Information System

 

This application manages Occupational Health in Solvay sites.

  • Industrial Hygiene - Controlling working conditions, evaluation of risk exposure (chemical, physical, biological or ergonomic risks)
  • Medical Monitoring - Examination and preventive advice, medical history, personal file.


It's located in InfoArea below:

 

Source system is PF7 (GRC system).

 

 

List of contacts:

  • Lysiane CHAYRAMY and Jérome POMMET (SBS Information Services) : EHS OH Process Expert
  • Célia GONZALEZ-ROUX (SBS Information Services) : Reporting Coordinator

Usage information


Used by industrial hygienists, occupational physicians and EHS managers of Solvay Group.

Around 77 users, 9 countries (28 sites in EU and LA).


History

Roles & Access

Roles and access


Role CodeRole DescriptionExplanation
ZR_RCS_EHS_A04 

Annual Report and Data Management

ZR_RCS_EHS_A06 
Occupational Diseases
ZR_RCS_CA_M43 
Upload Transaction (ZMX_UPLOAD)

Authorization objects


Authorization objectExplanation
Z_OH Based on C_HEALCTR




Dataflow overview


There are basically 3 types of flow:


  • Occupational Diseases (MVEHOD01)


  • Data Management (MVEHOH05)


          This model provides the following reports/indicators:

  • HBM (Human Bio-Monitoring) - to compare with BLV (Biological Limit Values) and BRV (Biological reference Values)
  • BMI (Body Mass Index) Indicator
  • Tobacco Indicator
  • Audiometry (WHO and IPA Indicator)


           Link to Data Management data flow


  • Annual Report (MVEHOH01 to MVEHOH04)

          A set of reports created per country with specific national regulations related to Annual Activity     


          Link to Annual Report data flow 


Functional and Technical rules on Workbench + Reporting

Rules & Explanations

 

Important Master Data:

  • C_HEALCTR (Health Center) - is where the authorization is based and attribute 0LANGU defines language for reporting
  • C_SRVNUM (Medical services) - is a medical case assigned to one Health Center and Employee (C_PERSID).
  • C_DIASRC (Diagnosis Source) - by the attribute C_DISRCG we define if an OD is notified / recognized / rejected
  • C_DIACD (Diagnosis Code) - by the attribute C_DIAGRP we define a group of diseases (respiratory, skin, etc). Used in SD query.
  •  C_ENTGRP (Entity group) - is the GBU

Employee assignment (Health Center x GBU x Workarea)


  • Employee can have only one health center for one period  (T7EHS00_PERHEAL -> DAEHOH10)
  • Employee can have one or more GBU during the same time (PA9907 -ZZENG -> DAEHOH14)
  • Employee can have one or more segment (work area) during the same time (HRP1001 -> DAEHOH19)

Medical Visit x Protocol x Aptitude advice


 

Occupational Diseases - Anomalies

 

A Medical case (C_SRVNUM) has an employee(C_PERSID) and OD code (C_DIACD).

It has different steps (C_DIASRC), which determines if an occurence is a notification, rejection or recognition of the OD.


C_PERSIDC_DIACD

Step1 (Date 1)

C_DIASRC-C_DISRCG

Step2 (Date 2)

C_DIASRC-C_DISRCG

1103 or 04 (notified)07 (recognized)
1203 or 04 (notified)08, 09, 10 or 11 (rejected)


C_LISTTYP is a rule to determine the anomalies in this process (C_LISTTYP = 1 is OK, other codes are anomalies)


C_LISTTYPDescription
1No anomalies
2Notification missing
3Multiple notification for the same case
4Notification after other(s) decision(s)




Dependencies with other applications

Data loadings

Info providers and objects loaded


Loading frequency


  • From PF7:  weekly process chain PC_EH_OH_META_0002.

  • From flat file: executed on demand by the users via transaction ZMX_UPLOAD. It raises an event to trigger PC_EH_OD_FF_01). This is used to upload "Occupational Diseases" data for sites that don't have Medexis.

Average performance


Key FigureEstimation
~ Average Process Chain Runtime2 hours
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

Record Keeping

Reporting

Queries End User Documentation


Main queries


Occupational Diseases:

  • BW_QRY_MVEHOD01_0001      Occupational Diseases of last 3 years (Core Query)
  • BW_QRY_MVEHOD01_0002      Occupational Diseases - Yearly Report by status (Core query)
  • BW_QRY_MVEHOD01_0003      Occ. Disease of last 10 years due to Agent (Core Query)
  • BW_QRY_MVEHOD01_0004      Occupational Diseases by Entity - Quaterly (Core Query)
  • BW_QRY_MVEHOD01_0005      Occupational Diseases of last 10 years - Entity (Core Query)
  • BW_QRY_MVEHOD01_0006      Occupational Diseases - Anomalies (Core Query) - Filter C_LISTTYP <> 1
  • BW_QRY_MVEHOD01_0007      Sustainable Development Report (Core Query) - Restricted KFs based on Diagnosis Group (C_DIACD-C_DIAGRP)



Main functionalities


Reports are executed via Solia portal. Each IVIEW contains Web Application containing one or more queries (contact to modify Solia links is Jose Cervera).


Language of the report depends on the language of the healthcenter (C_HEALCTR-LANGU). 
This is defined in the customer exit (CMOD) of Bex variable V_HEALTHCTR_EXIT_0001.


Reports display data from current year to Current Year – 2.


Transactions in PF7 to validate BW reports:

Broadcast

Maintenance

Known bugs

Recurring procedure

Planned Evolution


  • No labels