LegalFamily's "parcel tracking" for patients.

Built on technology so bleeding edge we've got the scars to prove it.

A Big Hairy Audacious Goal meets Unfair Competitive Advantage (timing, technology, insider knowledge)

• Location-restricted security.
• Live database backend (Google Firebase looks promising; problem with Elm integration?)
• Extensible plugin architecture for importing/syncing data with diverse systems.
• User-persona appropriate views
  • e.g Patient view help avoid missed appointments. Pill taking compliance.
    • Time to take your pill!
  • e.g Doctor view all the info in one place. Visibility of the trail of evidence and decisoions leading to the current diagnosis.
• Drug view: all the drugs "in play" on a ward. Highlight controlled drugs in nurse view (special rules apply).
• Jobs list: needs more state than just 'completed' to match refer/review pattern ordering scans: e.g add 'waiting' or 'in progress' states?

• Opportunities:
  • User-unfriendliness of existing legacy systems (e.g of Trakcare).
  • Unification could reduce wasted time, lost "bed days", improve accuracy of data (reduced re-entry).
  • Pressures/trends to open data silos (c.f OpenBanking).
  • Hook power-user early adopters via customisable, extensible.
  • Regional fragmentation allows a foot in the door on a smaller scale than huge national roll-out?
  • Demographic pressures. Elderly with complex interacting co-morbidities; need to get a holistic view.
  • Time spent searching for notes by nurses!
  • Trend to "Realistic medicine" (not clear how we actually help with this?)
• Threats/obstacles:
  • "Dogma" re existing systems.
  • Siloed data.
  • 28-year long PPI contracts with EMR providers.
• Strengths:
  • Mobile-first. EMR on the move. No more COWs (computers on wheels).
  • Uses robust and efficient advanced functional programming web-tech.
  • Clean "Material Design" UI.
• Weaknesses:
  • No good story on unified back end.

You'll need node (nodejs) via brew or apgt-get or whatever.

• elm-package install elm-lang/Http
• elm-package install debois/elm-mdl
• elm-package install elm-lang/navigation
• elm-package install evancz/url-parser

fakedata.js needs: npm install probability-distributions

• Run elm-reactor in this directory. It'll serve some webbystuff on localhost:8000. On that page, navigate to index.html OR
• Run ./BUILD

Update the autogenerated data files (PatientList.elm, JobList.elm... maybe others in future) by running ./fakedata.js in ./tools'. (This is done by the ./BUILD` script).

Data "schema" can be inspected in PatientPageTypes.elm

See community.css for some classes used int Main.elm and MDL overrides.

Misc annoyances:

• The "drawer" icon would probably be better vertical aligned with the text in the header if it had the same 10px padding.

• Is using a bleeding-edge technology noone has heard of crazy?

  • No: http://www.paulgraham.com/avg.html!
  • See also stuff out there about companies thinking they get an advantage from using obscure stuff like Erlang or even Haskell.

• https://medium.com/@jakeapeters/how-to-find-your-startups-unfair-competitive-advantage-859c9959a891

  • Startup advantages: Timing, Technology, Insider Knowledge.
  • Don't be distracted by competitor products & service.