Frequently Asked Questions

Below are a list of some of the questions we are asked by clients. If you have a question not listed in our FAQ, please feel free to ask us in an email.

General Questions

How often do new versions come out?

Clinical Office:MPage Editition has been extremely stable since initial release in 2018 and has needed little in the way of regular scheduled updates. Feature improvements are typically introduced entirely on the basis of client demand and through our own development of MPages.

Occassionally we may add some new data services when they seem like a logical fit for Clinical Office. We do not plan on modelling out the entire Cerner data model but rather just support common data requests. Custom data requests are much better served through highly optimized CCL scripts that are sourced through our generic CustomService data service.

Clients are notified through email as new versions do come available.

Can I request new features?

Our goal is to make Clinical Office as feature rich as possible. We understand that sometimes your current project needs may require functionality not available in Clinical Office. Our team is available to write CCL and Angular code as needed on a contract basis. Please contact our sales team to discuss your requirements.

Can you write my MPage? If you need us to write part or all of your MPage, please contact our sales team to discuss your requirements.
Do you offer training? We currently offer a two day training course in addition to our online documentation and tutorials.
Why can't I build something like Clinical Office myself? The development of Clinical Office:MPage Edition has taken many months of work with hundreds of hours of development time invested. While we are sure given enough time and resources, many of you could write something similar. The costs associated with the development time far out-weigh the cost of purchasing a Clinical Office license.
How experienced in Cerner is your development team? Clinical Office:MPage Edition has been developed completely by our founder, John Simpson who has been developing CCL scripts for 23 years and writing MPages for 10 years. There are very few people in the industry with the experience and background in CCL, MPages and more importantly the Cerner Data Model than John.

Technical Questions

Where do I host my MPage? In addition to the local Cerner WebSphere install (static content folder), your MPage can be hosted on any web server regardless of if it is your own web service, a Microsoft Azure App Service or any other online ISP.
Why Angular? Angular is better suited than JQuery when developing complex web applications such as MPages. Angular services, templates and routing offer a streamlined development process compared to the constant manipulation of the DOM needed in JQuery to accomplish the same task.
Which version of Angular does Clinical Office support? Clinical Office:MPage Edition was originally developed on Angular 2 (Version 6) and we test new versions as they are released to ensure compatibility. Currently Angular 12 is the latest stable release and Clinical Office works flawlessly with it.
How often are new versions released? New features and fixes are typically released the moment they have been fully tested and documented. Licensed clients are notified by email as new packages are updated.
How does Clinical Office fit in with current Cerner standards?

Cerner still heavily uses JQuery to develop their MPages and has developed their own practices for packaging and hosting MPages. At it's heart, Clinical Office:MPage Edition relies entirely on the Cerner developed XMLCCLRequest object making your MPages compatible with Cerner standards.

Clinical Office:MPage Edition can also be embedded into the Cerner component framework with an HTML IFRAME element. Insertion is simple and requires a few lines of additional code as well as the freely available iframe-resizer package. Later, when Cerner switches from Internet Explorer to Edge, we should have the ability to use Web Components to embed your Angular components without the need of an IFRAME.