Cerner Millennium Versions

[Andrea Coutu]

Is there a limitation on what version of Millennium a customer needs to be on to support the current FHIR integration? (Community works, etc)

What about hosted vs shared environments? Is there a limitation on what is supported through what's provided?

Thanks. 

[Benjamin Eichhorn (Cerner)]

Hi Andrea,

There are a number of packages that a clients domain needs to take before it can properly be onboarded. There are certain packages that can be skipped if that specific functionality is not wanted by the client. For example if a client has no intention of consuming the Slot and Appointment APIs they could skip taking the necessary packages that would cause those APIs to function. In terms of Community Works, Hosted vs Shared Environments, there should be no limitations in terms of functionality, assuming the domain(s) were onboarding correctly.

If you are a Cerner client feel free to browse our Reference Pages[1], specifically the "Install Cerner Ignite APIs"[2] section is a good first spot.

[1] https://wiki.cerner.com/pages/viewpage.action?pageId=1370794191

[2] https://wiki.cerner.com/display/public/reference/Install+Cerner+Ignite+APIs

Thanks,

Ben (Cerner)

[cou...@gmail.com]

Hi Benjamin,

Thank you for the above. From our understanding, a statement code is a required field for posting a payment transaction for Community Works, while for Cerner Millenium an encounter ID is required. Is this accurate? Would this limit the ability to post to either one or the other?

[Benjamin Eichhorn (Cerner)]

Hi,

I'm not sure I'm completely following. In general though, the restrictions we have listed per resource on fhir.cerner.com are going to apply overall, and, as long as a client has been onboarded to the Ignite APIs correctly you, as an app developer, will not find that a field is required in one domain that is not required in another (or vice versa). Our restrictions for required fields on creates will apply regardless of the domain you are on. 

Thanks,

Ben (Cerner)