FM/QUERY PORTFOLIO

Type help for commands or search nine case studies.

← Work index / Lifepack.id

Professional Experience Healthcare / health-tech

Health-Tech Data Infrastructure and Dashboards

Supported reliable data integration and built decision-ready reporting for a health-tech operation navigating evolving business needs.

Published with protected details
Lifepack doctor registry dashboard showing aggregate qualification and university distributions
Organization
Lifepack.id
Role
Data Analyst
Timeline
November 2024-April 2025
Stack
PostgreSQL · Metabase · Looker Studio · BigQuery · Python · Google Sheets · REST API · MySQL
My role

My contribution.

Work I directly owned or delivered within the broader team effort.

  1. 01

    Cleaned, validated, and reconciled operational data with the BI team.

  2. 02

    Developed and maintained more than 10 dashboards and reports for operational visibility.

  3. 03

    Integrated backend systems with a central database and escalated data-integrity risks.

Analysis frame

Assumptions / constraints

  • Operational reporting depended on integrating backend systems with a central database.
  • Doctor-registry data required validation and deduplication before loading into BigQuery.
  • Claims about delivery-cost effectiveness and aggregator growth cannot be published because definitions and evidence are unverified.

Technical judgment

Decision log

  1. 01
    Create a repeatable registry pipeline with validation and deduplication.Why

    Public doctor-registry extraction needed reliable preparation before central storage and reporting.

  2. 02
    Expose aggregate qualification and university distributions rather than row-level registry data.Why

    Stakeholders needed reporting while public disclosure had to protect contact and record-level details.

  3. 03
    Escalate data-integrity risks alongside dashboard delivery.Why

    Reliable operational decisions required trustworthy definitions and source data, not visualization alone.

Domain referenceMetric dictionaryView definitions +
GMV
Gross merchandise value; internal figures are withheld.
Deduplication
Removal or reconciliation of repeated registry records.
Row-level records
Individual source records excluded from public portfolio evidence.

Snapshot

I collaborated with the Business Intelligence team on data gathering, cleaning, integration, risk identification, and dashboard delivery while operational needs evolved.

The situation

Application and operational data needed to remain consistent and accessible as a health-tech business changed.

The problem

Backend systems, the main database, and stakeholder reporting required dependable synchronization, freshness, and clear risk escalation.

My responsibility

I supported integration and data quality, investigated risks, and translated operational data into stakeholder-facing reporting.

Approach

  • Synchronized backend systems with the main database.
  • Maintained data quality and freshness.
  • Identified and escalated data risks.
  • Developed and maintained more than 10 dashboards and reports.

Solution

The work combined data integration, monitoring practices, and stakeholder-facing reporting across Metabase, Looker Studio, and BigQuery. Published visuals are cropped to remove row-level records and contact fields.

Doctor registry pipeline

I structured a repeatable path from public doctor-registry extraction through validation and deduplication into BigQuery. The reporting layer exposed aggregate qualification and university distributions while keeping row-level registry records outside the public portfolio.

Prescription follow-up operations

I also supported visibility over prescription recall queues. The workflow separated incoming prescriptions, waiting or hold states, assigned follow-up, and recorded resolution so operational teams could inspect pending work without relying on an undifferentiated row-level export.

Outcome

The deliverables supported faster operational visibility and decision-making. Claims about delivery-cost effectiveness and aggregator growth are omitted because their definitions and evidence have not been verified for publication.

What I learned

In operational healthcare analytics, reliable definitions and escalation are as important as dashboard design. Public disclosure must also protect sensitive data.

Outcome Validated evidence

What changed.

Published outcomes stay within what can be supported by project evidence.

Developed and maintained more than 10 dashboards and reports

Supported operational visibility

Identified and escalated data risks

Contact Continue the conversation

Want to discuss how this system was built?