Minimum viable product (MVP) is a strategy that has gained rapid and widespread acceptance among the startup community. Used effectively, it can be a compelling strategy to evaluate product-market fit, which often is the largest risk facing a new medical software company. The idea of MVP is to focus a product or service on the key value that it provides to a customer.
MVP is about the minimal functionality that will do the job. The MVP will fail if you go any lower or remove any functionality from the MVP. So the trick is that if the product can work without any Functionality - please remove it from the MVP. Figuring out whether organizations or individuals will adopt the product often is the largest challenge facing new companies. The goal of MVP is to test the adoption and payment assumptions as early as possible. MVP is that product which has just those basic functionality that allows you to ship the product out.
A Healthcare delivery organization typically only needs a few core Modules to run the organization e.g. Registration, Appointment, ADT etc. We call these core modules are MVP. Rest of the functionality is fluff or Add-On that is not really essential but good to have.
The core blocks are representation of minimum functionality sets (also known as Minimum Viable Product Modules) within HDIS universe. All these core modules are required functions that any healthcare ecosystem will need. There can be add-on modules but the core are the minimum that must exist in a healthcare system. These modules caters not only the hospitals but also smaller health delivery centres like Clinics, Nursing Homes, PHCs, SCs, HWCs etc. But a PHC might not need full set of core functionality rather a subset of these MVP modules.
A Module has many Functionalities inside it. There could be 1 or multiple Microservices for each Functionality. Each Microservice has multiple data elements inside it. A Module has multiple Microservices. MDDS provides a library of 1000 Data Elements and 140 Code Directories. It is like a set of Lego blocks that you can use to build your own Apps.
We run a Social Entrepreneurship Accelerator [SEA] program. There are 25+ digital start-ups and HIS/EMR vendors working with us to implement the Digital Health standards and MVPs.
One of the technical approaches to comply with NDHB & EHR standards of India is implementation of microservices architecture with MDDS (Metadata Data Standards) as base.
Some of the SEA members had picked up microservices as a technical approach and have volunteered to contribute the same to our GITHUB repository that other SEA members and Government partners can benefit from. We would like to extend our gratitude and thanks to all the SEA members who have volunteered to build this open source community for India.
https://github.com/accesshdigital/sea-mvp-microservice .
Here is the link to access the HDIS MVP PHR Data Elements
https://drive.google.com/file/d/1HU7cf6D4MmNx9YzNO1DpX2TInRgue1N5/view?usp=sharing
The first set of microservices that we are releasing includes infrastructure microservices which serve as a base for setting up a microservice development environment. The description and implementation of these microservices is provided in the "readme " file. Please refer the same to get more detail about the uploaded microservices.
Please note we will be releasing more microservices in open source in an incremental way, whenever our volunteer SEA partners contribute the code to the GITHUB repository and is reviewed and approved by Access Health Digital.
How can the digital health opensource community benefit from these microservices codes?
1. New product development - If you are planning to build a new product , it is recommended to build the solution on microservices architecture using the shared microservices.
2. Legacy application - If you have a Legacy system and you dont want to disrupt your ongoing business model. then you have an option of building a Bolt-On translator layer on top of the Legacy system such that it populates the eObjects.
Note:- Soon we will also be releasing other MVPs like eObject schema, Open API specifications and other open source components in the GitHub.
Our collective endeavor is to convert our siloed health system to an interoperable digital health ecosystem. Let's get together and make it a success story!
Thank You for your continuous association with us.
-- ACCESS Health Digital --
Contact for Clarifications:
Access Health Digital
digital.health@accessh.org
No comments:
Post a Comment