Longitudinal care	The product needs to be designed to enhance the goal of improved longitudinal care, including both patient tracking and performance quality monitoring. Simple disease management protocols and data tracking should be modularized and accessible within the system.
Cross-Site Integration	The product should be integrated from the hospital, where human resource, electricity, and internet capacity are all substantial, to the primary clinics which are severely resource-constrained, to patients and community health workers, who would interface with the product on mobile devices.
Scalability	In everthing we do, we have to design for scale. This is particularly true because there is a strong push for us to expand the idea of pubic-private partnerships where the government is a payer and regulator and Possible is the direct implementer. If the technology can’t ultimately be scaled at a national level, then it is not worth the effort.
Simplicity	The tool should be elegant and simple for the user, designed for a healthcare provider with minimal computer literacy.
Reliability	Patients will suffer needless delays in care if the system is not exquisitely reliable in the setting in which the product is deployed.
Offline capability	The product needs to be online/offline capable, or at least intranet-capable, since, while Possible can get computers electricity 95% of the time, the internet (despite serious investments) is only 85% at best.