Chief Scientist; CEO

additional information
“The interoperability capabilities of the solution may be for naught if the solution does not also enhance patient-empowered privacy at the same time.”

“The patient should be in charge of decisions ….about privacy, whether to participate…to the extent possible.”

key insights
  • 1. ERROR/FRAUD DETECTION AND RECOVERY: even if system is 100% accurate, humans will introduce some error and/or fraud. The solution should understand the errors and fraud that humans can make and catch these errors as early as possible. Wherever they are caught, the system must be able to ensure that the errors are not propagated throughout the system and/or be able to reverse the propagation.
  • 2. SCALABLE/WIDE ADOPTION: the solution should a) use existing well-adopted standards (examples: ASPM, ANSII, HL7, etc); b) allow for the entire population of the world; c) ensure uniqueness of identifier for everyone; d) be applicable to every person and fetuses; e) independent of patient or provider’s language (eg. alpha characters are not universal and could present a problem for cultures that do not use alpha characters); f) integrate easily with existing IT systems (EHRs, ADT systems, EMPI systems); non-competitive with existing systems as much as possible.
  • 3. SIMPLE, FAST WORKFLOW/USER INTERFACE: The contender should outline how the solution changes relevant workflows (eg. patient registration, provider visit, billing, etc). Doctors and other staff should be able to describe the patient-facing workflows in 2 minutes and be understood by the patient. The solution should operate in “real-time” (eg. up to 3 minutes for registration)
  • 4. PRIVACY AND ANONYMITY: patients must be able to request privacy for a single visit or data item. The Solution should protect the patient’s health even when they have opted for privacy. For example, the doctor would see an alert on a medicine being prescribed without actually indicating what the private conflicting medicine is. Patient data should be trackable by public health and other researchers without sacrificing the anonymity of the patient.
  • 5. INTEROPERABILITY: Although the solution does not have to include interoperability itself, it must be able to identify where data for a particular patient resides in realtime. (eg. a patient could have data at primary care provider and specialists in the 4 different locations they have lived plus the Bahamas where they went into the hospital for a broken leg. The solution should be aware of this data in realtime if these providers are participating in the solution.)