The IndiMR Vision
  • A Proposal to Revolutionize India’s Healthcare
  • What Do We Propose?
  • Problems
    • Lack of Medical Facilities and Expertise
    • Lack and Unavailability of Medical Records
    • Lack of Data Standards and Interoperability
    • Increased Costs to People and Organizations
    • Lack of Reliable Data for Policy and Medical Research
    • Poor Spread of Health Insurance
    • Pilferage, Corruption, Fraud and Inefficiencies
  • General Contours of the Proposed Project
    • Why Open Source?
  • India’s Unique Position, Why India? Why Now?
  • Requirements and Unique Challenges
    • mHealth Centric
    • Blockchain Based
    • Knowledge-Based System – Separation of Knowledge from Software
    • Flexible and Composable
    • Collaboration and Workflow Orientation
    • Role of Artificial Intelligence
    • Integration of Miscellaneous Healthcare Associated Processes
    • Force Multiplier Effect – Orchestra Model
  • Benefits for India
    • Improved Healthcare for Indians
    • Public Health Impact
    • Health and Healthcare Policy Research
    • Spurt in Technology Innovation
    • Boon for Private Sector
    • Boost to Insurance Sector
    • Standards-Based Approach
    • Job Creation in Healthcare
    • Centralized Functions with Economies of Scale
    • Increased Soft Clout for India
  • Funding for Pilot Project and the Prototype System
  • Counter Arguments
    • "Indian Healthcare has so many basic problems, why not solve them first?"
    • "But This Has Already Been Done!"
  • Conclusions
  • Authors
Powered by GitBook
On this page
  1. Requirements and Unique Challenges

Flexible and Composable

PreviousKnowledge-Based System – Separation of Knowledge from SoftwareNextCollaboration and Workflow Orientation

Last updated 6 years ago

[]

Each feature of the system, down to the user interface elements, should be a standards-based modular component, allowing it to be used with other modules to compose a system that is tailored to the needs of any kind of health organization, and yet be interoperable with all other systems following same standards or built using the same approach. The effort should be to create a system with such high degree of end-user-friendly composability that it would allow even non-technical persons to create a useful system for their own use, or for use by their organization. This composability should cover the data used in the system, clinical decision support, workflow, and every aspect of the user-interface.

The modern day CMSs (e.g., WordPress, Joomla and Drupal) offer good examples for systems in which a person with no knowledge of writing programming code can configure very sophisticated systems that include features such as collaboration by large teams and presenting information to diverse users of the system in a manner that is useful to them. This is possible because of the plugin-based architecture these systems possess, allowing independent developers to provide new features encapsulated in their plugins.

This approach will be possible for NEMRS, if it is built from the ground up to be knowledge-based (as discussed above) with each component conforming to a set of international health data standards, and NEMRS specific standards for such components.

Go to the main IndiMR Site