What will The SANER Project Produce

It's a great question, and one I have in my head conceptually, but it's time to start writing this down:

1. A specification for how some things are going to work (basically a FHIR IG).
2. Two or more deployable FHIR Server images (1 .NET and 1 Java based) that can be used to support reporting of utilization data from hospitals, and viewing of that data by public health.
3. Interfaces delivered by major EHR, Health IT and Medical Device vendors that can populate the server above.
4. One or more components that can take data from that server and produce visualizations including:
1. Maps of facilities or regions that depict information about utilization
2. Graphs of trends over time for a specific facility or region that shows resource utilization and/or capacity.
5. One or more components that can consume data from that server and provide alerts about facilities or regions having (or no longer) being challenged.
6. One or more components that can consume data from that server and provide measure reports based on the available data.
7. Components that can bridge between what is delivered and existing solutions:
1. A way to quickly classify beds in an institution.
2. A way to transform the resulting data into  
8. A classification system for beds that allows systems to participate with some minimal level of supporting information and evolve to providing more granular data without disruption.
9. A classification system for reporting about mission critical equipment and supplies, and perhaps even a process or set of principles to use for establishing such classifications for future crises.
10. A virtual testing event where these materials can be tested safely, with simulated data.
11. A real world pilot where some of the components are deployed in secure environment and used with real world data.
12. A directory of endpoints where data can be sent to, or consumed from.

Components should be able to deploy with commonly available components on multiple platforms, including open-source database servers (SQL or NoSQL), and where cloud is available, to work with readily available cloud components (including both Windows and Linux servers).

No single organization will deliver all of these components.  Instead, members of The SANER Project will produce individual components that they can make readily available and easily installed for their customers, with minimal disruption.