Chingiz Mizambekov

Hospital billing · Reimbursement rules · Revenue integrity

Chingiz (Chase) Mizambekov

Lead Functional Analyst & Proxy Product Owner

Where reimbursement regulation becomes what a hospital actually bills

Belgium · Greater Tampa Bay Area, FL, USA

Both systems run on the same concepts, with different codes and different players.
  • 7+Years in hospital billing
  • 6Languages
  • IEEESenior Member

Now

Lead Functional Analyst & Proxy Product Owner

Qframe / Factura · March 2019 - Present, University Hospital of Antwerp (UZA), Belgium

Translating federal and regional reimbursement regulation into what actually gets billed, to whom, at what tariff. Oversight across the full invoicing lifecycle: creation, payment, rejection handling, corrections, re-invoicing, doctor payouts and accounting integration.

The work

For more than seven years my work has sat between care delivered and money received: the layer where federal and regional reimbursement rules turn into what a hospital bills, to whom, at what tariff.

  1. Reimbursement rules into billing rules

    Reading regulation as it is published and deciding what a billing system has to enforce because of it.

    Nomenclature, tariffs, application rules, and the conditions under which each of them holds.

    • Regulation analysis
    • Business rules
    • Tariffs
    • Legislative change
  2. The full invoicing lifecycle

    Creation, payment, rejection handling, corrections, re-invoicing, doctor payouts, accounting integration.

    The two failures that matter: rules that are missing, and rules that are wrong.

    • Invoicing
    • Rejections
    • Corrections
    • Reconciliation
  3. Requirements & process design

    Understanding the real process, the real exceptions and the real data before touching technology.

    Functional requirements, user stories, acceptance criteria, process flows.

    • Functional analysis
    • Exception handling
    • Acceptance criteria
    • Process flows
  4. Two systems, compared

    Since 2025 I have lived in the United States and have been reading its revenue cycle against the Belgian one, mechanism by mechanism.

    I write about the differences I notice; the concepts carry over, the codes and the players do not.

    • Revenue cycle
    • Revenue integrity
    • Comparative analysis

Experience

  1. Lead Functional Analyst & Proxy Product Owner

    Qframe NV · March 2019 - Present, Antwerp Area, Belgium

    Project
    Factura, UZA healthcare invoicing platform
    Client
    University Hospital of Antwerp (UZA)

    Translating complex healthcare reimbursement regulation and billing workflows into functional requirements and configurable business rules, so that billing teams can carry legislative changes through without developer intervention. Oversight across the full invoicing lifecycle.

  2. .NET Software Engineer

    Qframe NV · December 2018 - February 2019, Antwerp Area, Belgium

    Project
    Surveytool for Wonen in Vlaanderen (Living in Flanders)
    Client
    Vlaamse Overheid (Flemish Government)

    Secure web portal for social housing companies and their tenants across Belgium.

  3. .NET Software Engineer

    Qframe NV · November 2018 - December 2018, Antwerp Area, Belgium

    Project
    Huurschatter (Rent estimator)
    Client
    Vlaamse Overheid (Flemish Government)

    Web platform estimating house rental prices across Flanders from location, condition, schools, transport and other criteria.

  4. .NET Developer

    ABC-Groep.be · January 2018 - June 2018, Antwerp Area, Belgium

    Project
    Team intranet
    Client
    Belgian Bullets - national bobsleigh team

    Full-stack development with ASP.NET MVC 5, Entity Framework, SQL Server, Web API and Xamarin Forms.

  5. Fast Intervention Team

    Interparking · July 2005 - September 2016, Antwerp Area, Belgium

    Eleven years on the Fast Intervention Team: technical support, infrastructure maintenance (entry gates, networks, pay terminals, security cameras), client support, and problem-solving under pressure for 24/7 system reliability.

Memberships & credentials

Education

Languages