Min Tech Features Required for any Clinical Application

• FHIR based, RESTful using JSON read and write services
  • Supporting FHIR Resource & Profiles TBD ASAP
• Authorization (Josh Mandel (Unlicensed))
• Authentication
• Auditing
• Application Launch Context
  • Patient
  • Provider?
  • Location?
  • Encounter
• Simple transaction management (not long-running) (Scot Post van der Burg (Unlicensed))

Future Tech Features

• Governance model
• Service discovery
• Basic terminology services
• Simple eventing
• General Notification/Alerting/Messaging
• Advanced Terminology Services (subsumption, multiple representations)
• Event handling (pub/sub)
• Service Orchestration
• Long-running Transactions
• Decision Support Services
• System management (logging and monitoring)

Next Steps...

Next Month (June 2014)

• Build out technical feature teams (Rick Freeman)
• Schedule first Sub-Committee meeting
  • Determine sub-committee op mechs.
• Build rough schedule for first release of service definitions for prioritized Logica Clinical Use Cases
• Determine Dev Ops
  • Source Control
  • Documentation Standards

Next 3 Months (August 2014)

• Architectural Decision Ratification Process
• Application Distribution Model
• Determine required services and define service definitions
• Build technical architecture based on Logica prioritized Clinical Use Cases
  • This action item requires input from the Clinical Use Case Sub-Committee as a prerequisite