Use cases

Choose the use case that best represents your operation.

Six representative cases, from getting a scattered record in order to consolidating several plants. Each one documents its stages and the evidence it leaves behind. Fitting more than one is normal: scope and criteria are agreed after reviewing your process.

The six use cases

  1. 01Get the record in order and arrive with evidenceAudited by customers
  2. 02Determine fitness for duty with your own criteriaRegulated exposure
  3. 03Sustain preventive programs all year roundPopulation health program
  4. 04Consolidate several plants without mixing their dataMulti-plant with IT and Compliance
  5. 05Trace exposure when people move aroundHigh internal rotation
  6. 06Receive results from external laboratoriesFull and LiteTesting by an external provider

01Audited by customers

Get the record in order and arrive with evidence

The medical service is already running, but the information lives scattered. Bring in what exists, measure what is missing and have the evidence ready before anyone asks for it.

Starting point

The information exists, but it is spread across folders, emails and spreadsheets.

Every review forces the team to rebuild what had already been done. The real cost is not the fine: it is the week the team stops working to reassemble the evidence.

Record05 / 05
  1. Initial load

    Workforce and prior tests brought in

    Processed
  2. Exceptions

    Duplicates and unmatched rows resolved

    Confirmed
  3. Coverage

    Valid, expiring and pending by site

    Viewable
  4. Completeness

    Mandatory fields outstanding, by model

    Measured
  5. Evidence

    Documents, consents and audit log linked

    Exportable
Illustrative representation with fictitious data. The final flow, criteria and permissions depend on each organization’s configuration.
  1. 01Onboarding

    Bring in what already exists without capturing it again

    Problem
    Registrations and earlier tests live in loose files, and every new delivery is redone by hand.
    What GEXDI does
    Batch import checks the file before writing anything to the record, and reports the progress and the errors of the load.
    Output
    A workforce and a history brought in, with a record of what was accepted and what was rejected.
  2. 02Validation

    Resolve matches and exceptions before writing

    Problem
    A file with duplicates, or with people who have already left, contaminates the record from day one.
    What GEXDI does
    Column mapping and duplicate detection let you review every exception before confirming the batch.
    Output
    A confirmed batch, with the rejected rows identified and their reason.
  3. 03Coverage

    Know what is missing, worker by worker and site by site

    Problem
    Without a shared view, the gap is discovered once it has already expired.
    What GEXDI does
    Coverage relates what applies to each person with what is valid, expired or still pending.
    Output
    A searchable list of outstanding items and expiry dates by site and period.
  4. 04Completeness

    Measure how fully the record is actually captured

    Problem
    An incomplete record surfaces during the review, not before it.
    What GEXDI does
    The completeness report consolidates by business model and lets you drill down to the mandatory field that is missing.
    Output
    A percentage per model, with the detail of the fields left uncaptured.
  5. 05Evidence

    Deliver the review without redoing the work

    Problem
    Rebuilding the evidence costs days of work from the team that had already done the job.
    What GEXDI does
    Documents, consents, signatures and activity logs stay linked to the record and are exported subject to permissions.
    Output
    A body of evidence with owners, dates and traceability of access.

02Regulated exposure

Determine fitness for duty with your own criteria

Job requirements and fitness criteria are configured without reprogramming the system. The determination is left with its rationale, its restrictions and the professional behind it.

Representative case

Someone is about to take a job with noise exposure and work at height, and the fitness decision has to hold up in writing.

The physician needs history and valid tests. Safety needs to know which restriction applies. The day the decision is questioned, it has to be explainable.

Record06 / 06
  1. Job requirements

    Noise, height and exertion declared

    Configured
  2. Examination event

    Periodic opened with required tests

    Scheduled
  3. Tests

    Audiometry and spirometry normalized

    Comparable
  4. Compatibility

    Profile assessed against job requirements

    Assessed
  5. Determination

    Fit with measures · noise exposure restriction

    Signed
  6. Validity

    Reassessment scheduled at expiry

    On the calendar
Illustrative representation with fictitious data. The final flow, criteria and permissions depend on each organization’s configuration.
  1. 01Requirements

    Describe what the job demands, not just which exam is due

    Problem
    Fitness is decided well, but the reasoning rarely ends up written next to the decision.
    What GEXDI does
    Job requirements and the risk profile are configured by catalog and kept versioned.
    Output
    A job with its demands declared and its risk profile attached.
  2. 02Scheduling

    Open the examination event that applies

    Problem
    Pre-employment, periodic, exit and return follow different criteria that a spreadsheet cannot tell apart.
    What GEXDI does
    The health event is opened by purpose and pulls in the tests the organization defined for that job.
    Output
    An open event with its list of required tests and its target date.
  3. 03Normalization

    Make results from different sources comparable

    Problem
    Every laboratory delivers in its own format, and two audiograms are not always read the same way.
    What GEXDI does
    Results are normalized to a common severity scale so they can be compared across types and over time.
    Output
    Tests brought in with a consistent reading and their history available.
  4. 04Assessment

    Weigh the person against what the job demands

    Problem
    An isolated result does not say whether this person can hold this particular job.
    What GEXDI does
    The criteria engine evaluates the clinical profile against the configured requirements and shows which rule was applied.
    Output
    A compatibility assessment with the rules behind it in plain sight.
  5. 05Determination

    Issue the fitness decision with its rationale and its restrictions

    Problem
    A bare status does not explain what was reviewed, who decided or which condition must be respected.
    What GEXDI does
    The determination documents outcome, rationale, restrictions, date and responsible professional, and produces the certificate.
    Output
    A fitness decision tied to the worker, to the job and to whoever signed it.
  6. 06Validity

    Reassess before it expires

    Problem
    An expired fitness determination is noticed when someone looks for it, not when it lapses.
    What GEXDI does
    Validity is attached to the determination and feeds the coverage and the outstanding items for the period.
    Output
    A reassessment scheduled, with its owner and its date.

03Population health program

Sustain preventive programs all year round

The half almost nobody sees: chronic conditions, prenatal care, lactation, vaccination and musculoskeletal, with signed periodic visits and measurable adherence.

Representative case

The company wants to move from treating isolated consultations to accompanying its people through the year.

Follow-up on a chronic condition or a pregnancy is kept in a notebook. When that person is absent, or whoever treats them changes, the case loses continuity and there is no way to report on the program.

Record05 / 05
  1. Target population

    Candidates for follow-up identified

    Identified
  2. Program

    Chronic conditions and prenatal care opened

    Enrolled
  3. Next visit

    Periodic visit booked with notice

    Booked
  4. Progression

    Visits signed and comparable with each other

    Recorded
  5. Indicators

    Coverage and adherence in aggregate by site

    Reportable
Illustrative representation with fictitious data. The final flow, criteria and permissions depend on each organization’s configuration.
  1. 01Detection

    Identify who needs to be accompanied

    Problem
    Findings that warrant follow-up stay inside a note and never become a program.
    What GEXDI does
    The information in the record makes it possible to identify the population each program applies to.
    Output
    A target population that can be reviewed by site, area and job.
  2. 02Enrollment

    Open the program that fits each case

    Problem
    Without a container of its own, follow-up blends into ordinary consultation and gets lost.
    What GEXDI does
    Chronic conditions, prenatal care, lactation, vaccination and musculoskeletal each have their own flow and their own progress track.
    Output
    A case opened inside the program, tied to the person’s record.
  3. 03Scheduling

    Turn the next review into a real appointment

    Problem
    A recommendation with no date and no owner never comes back around.
    What GEXDI does
    Visits are scheduled in the medical calendar and the worker gets the notice when that channel is enabled.
    Output
    Periodic visits booked with their owner assigned.
  4. 04Visit

    Record each visit as part of a progression

    Problem
    An isolated consultation does not show whether the person is improving or getting worse.
    What GEXDI does
    Every visit is documented and signed inside the program, and stays comparable with the previous ones.
    Output
    A progression you can review, with its measurements, notes and signatures.
  5. 05Adherence

    Report the program with data instead of impressions

    Problem
    Leadership pays for a medical service that reports nothing measurable.
    What GEXDI does
    Indicators show coverage, activity and adherence in aggregate, segmentable by period and site.
    Output
    A view of the program that preserves the confidentiality of the individual case.

04Multi-plant with IT and Compliance

Consolidate several plants without mixing their data

Each site operates with its own criteria and sees only its own. Corporate reviews the consolidated view without that meaning access to individual data.

Representative case

Each plant keeps its own format and leadership has no single figure that compares across sites.

Corporate needs to compare coverage and progress. IT needs people to sign in with the account they already use. Compliance needs to know who looked at what. None of the three needs anyone’s diagnosis.

Record06 / 06
  1. Structure

    Companies, sites and jobs modeled

    Defined
  2. Identity

    Federated access over OIDC

    Connected
  3. Permissions

    Access by role and authorized site

    Applied
  4. Criteria per site

    Local catalogs and rules configured

    Running
  5. Consolidated

    Indicators comparable across sites

    Available
  6. Audit log

    Relevant lookups and changes recorded

    Traceable
Illustrative representation with fictitious data. The final flow, criteria and permissions depend on each organization’s configuration.
  1. 01Structure

    Model the organization the way it actually operates

    Problem
    A single pool of workers does not represent a company with several plants and several legal entities.
    What GEXDI does
    Companies, sites, departments, areas and jobs are modeled with their own catalogs per site.
    Output
    A structure where each person sits where they actually work.
  2. 02Identity

    Sign in with the corporate account that already exists

    Problem
    One more password per system is one more password that gets shared or forgotten.
    What GEXDI does
    Access is federated with Microsoft Entra ID, Okta or another OIDC-compatible provider, with two-step verification as the local alternative.
    Output
    Joiners and leavers governed from the organization’s directory.
  3. 03Permissions

    Bound what each profile sees, and at which site

    Problem
    Opening the full record to everyone is the fastest way to lose control of clinical data.
    What GEXDI does
    Permissions are assigned by role and by site, and one user can switch between the sites they are authorized for.
    Output
    Access bounded to each person’s responsibility and location.
  4. 04Operation

    Let each plant work with its own criteria

    Problem
    Imposing a single criterion on plants with different exposures forces people to operate outside the system.
    What GEXDI does
    Catalogs, jobs and criteria are configured per site without breaking the shared structure.
    Output
    Sites that run on their own rules and remain comparable.
  5. 05Consolidation

    Compare sites against a single definition

    Problem
    Each plant calculates its figures its own way and the consolidated view means nothing.
    What GEXDI does
    Indicators are built on the same records and segmented by period, site, area and job.
    Output
    A comparable corporate view, within the permissions of whoever is looking.
  6. 06Audit

    Be able to answer who looked at what

    Problem
    Health data is the most sensitive the company handles, and access to it is rarely logged.
    What GEXDI does
    The activity log keeps relevant lookups and changes, and clinical files are stored encrypted.
    Output
    An audit log you can search, able to support an internal or external review.

05High internal rotation

Trace exposure when people move around

Changes of area, job and shift stay in the work history, so a clinical finding can be related to the exposure that preceded it.

Representative case

Someone has passed through three areas and two shifts in eighteen months, and a hearing finding shows up.

To support or rule out a link to the work, you need to know where they were, for how long and with what exposure. That history usually exists in payroll, not in the clinical record.

Record05 / 05
  1. Movement

    Change of area and shift, dated

    Recorded
  2. Gap

    Tests the new job does require

    Identified
  3. Assessment

    Exam opened due to job change

    Pending
  4. Work history

    Three areas and two shifts, with dates

    Complete
  5. Rationale

    Finding, exposure and determinations linked

    Viewable
Illustrative representation with fictitious data. The final flow, criteria and permissions depend on each organization’s configuration.
  1. 01Movement

    Record the change when it happens

    Problem
    A change of area or shift is reported to payroll and never reaches the medical record.
    What GEXDI does
    Area rotations, job changes and shift changes are recorded with their date.
    Output
    A dated movement inside the person’s work history.
  2. 02Recalculation

    Review what the new job demands

    Problem
    A new job may require tests the previous one did not ask for, and nobody notices.
    What GEXDI does
    The change recalculates the applicable requirements and shows the difference against what the person currently holds.
    Output
    An explicit gap between what is required and what is covered.
  3. 03Trigger

    Turn the gap into a real assessment

    Problem
    Spotting the shortfall is useless if it does not become an appointment with an owner.
    What GEXDI does
    The corresponding examination event is opened and enters the coverage for the period.
    Output
    A pending assessment assigned and visible to whoever coordinates.
  4. 04History

    Keep the full timeline

    Problem
    Without the sequence of jobs and shifts, the record only shows where the person is today.
    What GEXDI does
    The work history keeps every stretch with its dates, alongside the clinical history.
    Output
    An exposure timeline you can review by period.
  5. 05Rationale

    Be able to explain the case when it is questioned

    Problem
    In litigation or a review, reconstructing after the fact counts for little.
    What GEXDI does
    Findings, tests, determinations and exposure stretches stay linked to the same record.
    Output
    A record that lets the sequence be reviewed with dates and owners.

06Testing by an external providerFull and Lite

Receive results from external laboratories

Tests performed by an external provider enter the record without being retyped, attached to the right person and with their expiry dates in plain sight.

In Full it feeds the clinical history documented by your own medical service. In Lite it is the core flow of the product.Explore GEXDI Lite

Starting point

The tests are run by an external laboratory and the result ends up as a PDF that someone files in the plant folder.

Whether or not there is a medical service on site, the result has to reach the record without being retyped and stay attached to the right person. With an in-house physician it feeds the clinical history; without one, it sustains the follow-up HR coordinates.

Record05 / 05
  1. Template

    Format agreed with the provider

    Defined
  2. Import

    Batch of results brought in

    Processed
  3. Matching

    Results tied to the right worker

    Validated
  4. Coverage

    Expiry dates and pending items by site

    Viewable
  5. History

    Record preserved worker by worker

    Continuous
Illustrative representation with fictitious data. The final flow, criteria and permissions depend on each organization’s configuration.
  1. 01Template

    Agree on a format with the provider

    Problem
    Every laboratory delivers differently, and every delivery forces a retype.
    What GEXDI does
    During implementation a structured template is defined, covering the tests included in the service.
    Output
    An agreed format the provider can repeat with every delivery.
  2. 02Import

    Load the whole batch in one go

    Problem
    Typing in dozens of results by hand eats the time of the person who should be coordinating.
    What GEXDI does
    Structured import brings the results in and shows the progress of the load.
    Output
    A batch brought in, with its processing report.
  3. 03Validation

    Check the matches before calling the load good

    Problem
    A result attached to the wrong person is worse than not having it.
    What GEXDI does
    The system checks every row against the workforce roster and isolates the exceptions.
    Output
    Results attached to the right worker, with the exceptions flagged.
  4. 04Coverage

    See the state of the workforce at a glance

    Problem
    Without a view by site, an expiry shows up once it has already passed.
    What GEXDI does
    Coverage and expiry dates are reviewed by worker, site, area or purpose of the exam.
    Output
    A reviewable state of what is valid, expiring and pending.
  5. 05Follow-up

    Close the open items and keep the history

    Problem
    Changing provider usually means starting the history from scratch.
    What GEXDI does
    Results already loaded stay in the record regardless of who runs the tests that follow.
    Output
    A history per worker that survives a change of provider.
Boundaries by responsibility

Each profile needs a different answer from the same process.

Usefulness is not about showing everything to everyone, but about delivering the level of information needed to treat, coordinate and oversee.

Medical team

Authorized clinical detail

Reviews history, records care and tests, issues fitness determinations and maintains follow-up.

Access depends on clinical permissions, site and assigned responsibilities.

HR and operations

Status to coordinate

Reviews coverage, expiry dates, outstanding items and authorized operating conditions.

Clinical detail should not be assumed visible; it is validated field by field during configuration.

Leadership and EHS

Coverage and trend

Reviews aggregate indicators by site, period or program according to their permissions.

The aggregate view and access to individual cases must be defined independently.

The demonstration should confirm, with fictitious data, what each profile can view, modify, sign and export.

Resulting evidence

A dashboard is no substitute for the records behind each indicator.

A review must be able to move from the aggregate view down to the authorized records that explain dates, owners, decisions and follow-up.

What has to be documented

  1. 01Work context

    Company, site, area and job related to the event.

  2. 02Care and tests

    Notes, results, documents and findings added to the record.

  3. 03Fitness and restrictions

    Decision, rationale, date and responsible professional.

  4. 04Continuity

    Program, medical leave, reassignment or review that continues after the event.

  5. 05Traceability

    Signatures, changes and relevant activity within the configured scope and permissions.

Rollout process

How it goes live, stage by stage.

Implementation moves through agreed stages. What enters each one, in what order and how far the scope reaches is the organization’s decision: this describes the process, not a mandatory path.

  1. 01Discovery

    The current process, the available sources of information and who takes part at each step are reviewed.

  2. 02Configuration

    Catalogs, jobs, criteria, roles and the outputs the organization expects are set up.

  3. 03Validation with data

    Testing runs on fictitious or previously anonymized data to review capture, migration and exceptions.

  4. 04Go-live

    The organization decides what enters operation, at which sites and with which modules, and when to expand.

Timelines, integrations and migration volume are estimated after reviewing the process and the quality of the available information. The decision on scope belongs to each organization.

A demonstration built on one case

Let’s review a fitness decision and the evidence your operation needs.

We walk through work context, assessment, determination, follow-up and permissions using a case representative of your process.

Review a case against your operation