Thanks @brady.miller, Here are some thoughts.
I suppose the easiest is to take a look at a public test server to see what others are testing. You can go here: https://fhirtest.uhn.ca/
My goal is to get most of the informative resources that would cover our basic chart that is of use to patient or other providers. Medication Statement, Observation and Condition comes to mind(Patient, Encounters and Practitioner are mostly done). Remember when working a resource, end points to other resource may be required with that resource required to be already on the server, otherwise server will reject.
I’m thinking that support resources such as Organization, Practitioner and Location be auto created/updated from the dashboard to support other Profiles.(I’ve got this)
Another concern is coding systems( coding systems are closely tied to FHIR). We generally don’t record snomed that I can tell(I think even loading codes is optional) along with our encounter form is in need of updating to better support FHIR and Institutional with making it not so closely tied to billing for encounter status and disposition.
Once we have a working set of profiles and resources, we know how to set the conformance and capability statements for our implemented server.(I think we can also do that with the Dashboard provider client.).
I think we have a good start with a REST and HTTP class for clients, resource class and client endpoint class and i’m working on a library for auto sending resources from OpenEMR scripts such as appointments, encounters e.t.c, yet much too do.