Reference Architecture

The Reference Architecture will describe the following:

1. The specific common services and corresponding “units of functionality” expected/required in a Healthcare 2.0 ecosystem.
2. The interfaces provided by each service to expose the data and/or functionality that the service is deemed to be authoritative for.
3. The information payloads and standards used to describe the information (e.g., data models and messaging standards such as FHIR) used to communicate with services.
4. The common patterns for using services and the orchestration of services that solve common business needs.
5. The organization of the services stratified into logical layers based on the nature of the service and the level of commonality of a given service. As a rule of thumb, services that are very common tend to be more generic in nature and closer to what is considered base “infrastructure”. Services that are less common tend to sit on top of the more common services and are more closely aligned to healthcare business functions (e.g., ordering). The services taxonomy will introduce layers based on this continuum to provide guidance on how services interact and how they are consumed by other applications.

Working group meets alternate Fridays at 12:30 ET with July 19th being the next call.

https://global.gotomeeting.com/join/257312965

United States: +1 (224) 501-3412<tel:+12245013412,,257312965>
Access Code: 257-312-965

Contacts Preston Lee, Bo Dagnall, Ken Rubin, Lorraine Constable, Scott Narus

Meeting Notes

Working Documents