Call Minutes – 2015-08-06
Discussion of Scope:
Gora: Need to make sure that the scope of our effort clearly defines why it is that HL7 is taking a point
of view on cloud. Need to relate the HL7 standards into the cloud environment as part of the work
product.
Ken: Note that scope should consider both the standards directly, as well as software that has
implemented those standards.
Stefano: Need to also address the architectural viewpoint, and implications of a cloud architecture on
implementation of standards and systems.
Gora: Helps to establish transition from classic systems composition into a more modern, modulebased, dynamic system environment.
Stefano: Present spectrum and analysis of alternatives. Not just technology aspect, but impact on
organizational dynamics.
Gora: Impacts on innovation, technology insertion, assimilation of innovation.
-
Cost impacts
(See security discussion from 7/26 – PII/PHI, security implications, privacy, etc.)
When does infrastructure topology matter (e.g, when do we care if it is cloud, and when do we not)
Candidate HL7 Portfolio Items to consider within scope:
-
HL7 SOA Service Standards (HSSP); Coordination of Care Standard
EHR Functional Model
Mobile Health Consumer Functional Framework
FHIR
HL7 Security Standards
NOT IN SCOPE:
-
How to design a specific solution; How to build software on cloud; Product or platform
recommendations; supplier recommendations;
IN SCOPE FOR BROADER CONTEXT (e.g., appendix or educational material – light touch):
-
Private, public, hybrid cloud
-
Cost/cost implications
IAAS, SAAS, PAAS
Primary Target Audience:
-
Implementation manager – the one whom has responsibility for acquisition, integration,
and deployment of solutions into customer enterprise; “Inside architect”
Product owners/managers – making strategic product decisions around market offerings
Consumers whom are looking at cloud based solutions for their needs (patient portals, EHR
implementation, etc. Users. Secure, standards based.
Support for “inside architects” within customer orgs
Business Stakeholders/Decision-makers – help to establish business case for cloud, and/or
to help make informed decisions around resource obligations re: cloud.