Hi,
All of our functionality that we expose is documented here:
https://fhir.cerner.com. You'll note that no financial resources are exposed (largely due to maturity and priority issues), and in DSTU 2, there's no good way to represent some of what you've mentioned above. For example, even in the upcoming R4 release from HL7, there's no model to post a payment from a patient or guarantor within the standard.
SMART on FHIR supports a launch in context. You can read more about what context can be returned by the standard here:
http://docs.smarthealthit.org/ If launched from the EHR (provider user), the patient id and encounter would come back, which can be used to search the FHIR API for information. Even if we supported Account, it's not a standard item returned in SMART.
For patient launch, there's a standalone launch that would allow you to get the patient id or search for patients that the user has authorization for. Again, you would need to use the SMART context + FHIR APIs to build out this workflow. You can read more about SMART and Authorization support on our site above.
Our FHIR server is cloud hosted. As such, the API is consistent for all our clients regardless of code base.
Millennium is likely the EHR that the Client supports, though you can confirm with them in your discussions.
Regards,
Jenni