Sorry I missed this but for Smart on Fhir a server to support (HSPC) is being tested and can be implemented fairly soon but still need to profile to specific value set and terminologies to support OpenEMR. Regardless if we provide a server setup and install for OpenEMR or user wants to interface with a public/private server of their choosing, too me, the most critical part of implementing FHIR is integrating our patient data to the server. The current plan is to create libraries and classes that allow core chart resource data to automatically update the server as chart data is created/updated making the interface and translation of resources key. I think once this is finished the imaginations can run wild for the client goodies.
I further plan that as I create resource methods to populate the server, a companion method is created to import resource to OpenEMR thus edging closer to a HIE of sorts.(Also working a HL7 MLLP sender)
This is my take and hopefully not a naive one.
Regarding timeline: for the core resources, possibly two weeks when I hope to have at least demographic, encounters, procedures(observations), conditions(problems) and medication statement.