Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

1 1 anatomy of an app

65 views

Published on

This presentation provides an insight into the anatomy of an eHealth app and different approaches to building healthcare applications.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

1 1 anatomy of an app

  1. 1. Dr Ian McNicoll Anatomy of an eHealth app
  2. 2. Anatomy of an eHealth app
  3. 3. Anatomy of an eHealth app
  4. 4. the ‘application’ The part of the software that the user sees and works with
  5. 5. Anatomy of an eHealth app
  6. 6. Anatomy of an eHealth app
  7. 7. the “persistence layer” How and where the information is physically stored or ‘saved’ in a local database, in the ‘cloud’ usually the app must know the physical layout ‘schema’ of the database to know how to retrieve the information e.g. exactly where patient ID ,
 systolic and diastolic BP etc are located in the database The app must also understand the database query language SQL, mongoDB, Cassandra
  8. 8. Anatomy of an eHealth app
  9. 9. Anatomy of an eHealth app
  10. 10. the ‘information model’? Any definition of the structure and content of information that should be collected or shared A ‘minimal dataset’ A message or interface definition Internally every application has some kind of information model Sharing information requires developing shared information models
  11. 11. the ‘information model’ Is used to manipulate information in the computer’s memory Often written in a specific program language Generally locked-in to each application Not easily shareable
  12. 12. What is in an API? Application Programming Interface how modern web apps talk to each other request/ receive some sort of ‘structured content’ https://ehrscape.code-4-health.org/rest/v1/ composition/12345-123?format=STRUCTURED
  13. 13. Information models power the web
  14. 14. Information models power the web
  15. 15. Mismatched clinical information models
  16. 16. ‘Megasuite’ architecture
  17. 17. ‘Megasuite’ architecture
  18. 18. ‘closed platform’ architecture
  19. 19. ‘closed platform’ architecture
  20. 20. Shared models - Closed platform
  21. 21. Multiple information models = high-cost, non-interoperable systems
  22. 22. Multiple information models = high-cost, non-interoperable systems app app app app app
  23. 23. Moving information .. sharing information models … Application-specific Application-specific Vendor neutral exchange modelVendor-specific platform Vendor-neutral platform Application-specific
  24. 24. Best of breed integration
  25. 25. Best of breed integration
  26. 26. Best of breed integration
  27. 27. Best of breed integration
  28. 28. Best of breed integration
  29. 29. ‘the open platform’ ‘free the data’ In the future, the organisation or company that handles your health datastore will be separate from the company or organisation that build your applications.
  30. 30. the ‘open platform’ must be based on a common, open information model open specifications open source clinical content definitions
 other parts of the ecosystem need not be open source
 critical infrastructure for new app developers substantially faster development much lower barriers to market no vendor / technology lock-in
  31. 31. clinician-led, open platform
  32. 32. openEHR Rest API + AQL ’open platform’ architecture open Information Model App App App
  33. 33. openEHR Rest API + AQL ’open platform’ architecture App App App
  34. 34. openEHR CDR openEHR Rest API + AQL ’open platform’ architecture App App App
  35. 35. openEHR Rest API + AQL ’open platform’ architecture App App App
  36. 36. openEHR Rest API + AQL ’open platform’ architecture App App App
  37. 37. openEHR Rest API + AQL ’open platform’ architecture App App App
  38. 38. openEHR Rest API + AQL ’open platform’ architecture App App App
  39. 39. openEHR Rest API + AQL ’open platform’ architecture App App App
  40. 40. Clinicians in control
  41. 41. The ‘bi-modal’ EHR? Bimodal IT is the practice of managing two separate, coherent modes of IT delivery, one focused on stability and the other on agility. Mode 1 is traditional and sequential, emphasizing safety and accuracy. Mode 2 is exploratory and nonlinear, emphasizing agility and speed. open Platform + Legacy EPR

×