NorviTech / Consulting / DA2 vs Discern Explorer
DA2, Discern Explorer and the Reporting Portal
Three names from one reporting family in Oracle Health (Cerner) Millennium, and which one a given request actually needs.
The short version
Discern Analytics 2.0 (DA2) is where most reports get built: a query and report designer for Millennium data, used by report writers and analysts rather than programmers. Discern Explorer is Cerner Command Language (CCL), the scripting language programmers write against the Millennium database. The Discern Reporting Portal is where people run reports, and it is built on the DA2 framework.
They are not rivals. A hospital running Millennium usually has all three, and the useful question about any request is which one it needs, because that decides who can build it and how long it waits in a queue.
Side by side
| Discern Analytics 2.0 | Discern Explorer (CCL) | Discern Reporting Portal | |
|---|---|---|---|
| What it is | A designer for queries, data cubes and formatted reports | A query and scripting language against the Millennium database | A place to find and run reports |
| Who uses it | Report writers, analysts, super users | CCL programmers | Managers, supervisors, anyone who needs the output |
| Where it runs | A desktop application and a web application | Programs compiled into the domain, run from menus, schedules or other programs | The browser |
| Security | Governed by the domain’s own security; what a user can see depends on their position and grants | Shares DA2’s security, so a report visible in one is visible in the other | |
How they fit together
Since Millennium 2018.01, Explorer Menu, the old launcher for Discern Explorer programs, is no longer supported, and DA2 took its place as the front door. The Reporting Portal uses the same framework, so reports published in DA2 show up in the Portal and the other way round. The Portal can also run other report types side by side, including Discern Explorer programs and, where a site has them, BusinessObjects reports and data cubes, with the option to run a long report in the background and collect the output later.
In practice that means a user rarely cares which tool built a report. The distinction matters to whoever has to build it or fix it.
Which one does a request need?
Build it in DA2 when
The question is a list, a count or a trend over data the domain already exposes: appointments, charges, encounters, census, orders. Prompts for a date range or a location, grouping, subtotals and crosstabs are exactly what DA2 is for, and a report writer can own it after hand-over.
It needs CCL when
The request writes back to the database, needs procedural logic a query cannot express, or has to run as part of another program. Those belong with a CCL programmer, and pretending otherwise produces a DA2 report nobody can maintain.
It only needs the Portal when
The report already exists and the real problem is that the right people cannot find it or run it. That is a publishing and security change, not a build.
A good share of what lands in a CCL queue is the first kind. Moving it to DA2 shortens the wait for the requester and leaves the programmers with the work that genuinely needs them. When a request truly needs CCL, the honest move is to say so at scoping rather than half-way through the build.
Next
- Discern Analytics 2.0 consulting — report builds, scheduled extracts, dashboards and training
- Automating scheduled DA2 extracts into a dashboard
- Why a DA2 report’s totals come out inflated
- Choosing a DA2 report’s date window, and its time zone
- Getting DA2 data into Google, Azure or your warehouse
- DA2 reporting on the Continuum and CommunityWorks domains
Oracle, Oracle Health, Cerner, Millennium and Discern are trademarks of Oracle and/or its affiliates. NorviTech is independent and is not affiliated with, sponsored by or endorsed by Oracle.