Rexia: product design and UX/UI for a financial intelligence platform in healthcare

Rexia is a financial intelligence platform for health systems: payers, social health insurers, medical centers and institutions that work with complex administrative rules.

I work as a product designer inside the team. Because of confidentiality, this case shows no screenshots or internal data: it describes the kind of problem and how I approach it.

Make rule-heavy processes understandable: which services an agreement covers, under what conditions, at what rates and from what date, and how each service is authorized and audited. The interface has to organize that complexity without hiding it.

• Structure agreement and authorization information so it can be read and maintained.
• Design flows that reflect the business rules clearly.
• Keep statuses, results and the history of each process visible.

I am responsible for product design: flows, information structure, UX and UI for complex processes. I work across disciplines with product and engineering, and I document decisions with diagrams and specifications.

• Complex administrative rules that depend on the type of institution.
• Sensitive information: no screens or internal data can be shown.
• A product that keeps evolving and is designed together with product and engineering.

1. 1Understand the domain rules together with product.
2. 2Map flows and information structure with functional diagrams.
3. 3Document flows and product specifications for the engineering team.
4. 4Design the UX and UI of each process and refine it with the team.
5. 5Use AI tools to explore alternatives and document design solutions; the decisions are mine.

• Model the flow and the information structure first, and the interface after.
• Treat statuses, traceability and change history as a core part of the experience, not an add-on.
• Document each flow so product and engineering work from the same understanding.

The work is organized around two functional areas of the product.

• Agreement management: services and codes, coverage and conditions, rates, copayments and caps, validity dates, Excel import, and version and change history.
• Authorizations: authorization flows, analysis of services and items, display of statuses and results, and traceability and audit.

Functional diagrams, flow documentation, product specifications and AI tools to explore and document design solutions.

Product context: Angular, NestJS, Prisma and Supabase in a monorepo. This is the engineering team's stack; it is not my code.

• Flows and information structure for agreements and authorizations.
• UX and UI design for complex processes.
• Functional diagrams and flow documentation.
• Product specifications.

Current status: ongoing and confidential work, with no screenshots or internal data. No metrics are reported.