Hjälpmedelsportalen — Assistive Devices Portal

The Healthcare Administration (Hälso- och sjukvårdsförvaltningen) is responsible for ensuring that residents of Stockholm County have access to good and safe medical and dental care. The Assistive Devices Portal is a web-based system, developed in 2025, for managing prescriptions for assistive devices for people with various disabilities within the Stockholm Region, as well as validating billing.

An API layer was built that followed new requirements and allowed over 300 suppliers to integrate their legacy systems — originally built in 2005. Robin took over responsibility from the previous solution architect, developer, communicator, and tester working with suppliers, to ensure rapid development cycles and maintain a flexible architecture saving weeks of development time.

As Technical Owner Robin owned the external integration end-to-end: planning, prioritization, and quality assurance from requirements to production. He led communication with suppliers' technical leads and developers, managed the backlog, and coordinated internal tracks so that integrations and release cycles stayed on schedule.

As Solution Architect Robin designed the API contract, data and process flows, and data validation for the external integration layer. He defined error/retry strategies, logging, and traceability for robust operations and high availability.

As .NET Developer Robin implemented integration endpoints, service layers, retry and error handling logic, regression tests, and validation logic in .NET, optimized database interactions, and exposed REST APIs with Swagger/OpenAPI.

As Tester Robin planned and drove continuous testing (functional, E2E, and data quality) for supplier flows, defined acceptance criteria and test cases, and delegated execution to testers. He used logs/metrics to verify flows and catch regression risks before production deployment.

As Requirements Manager Robin took responsibility for the requirements picture on the supplier side: identifying unknown business rules together with suppliers, syncing these against known internal requirements, and translating agreements into user stories, acceptance criteria, and supplier documentation.