Introduction
Review the following guidelines to ensure the best results for your Clarity reports and extracts and to maintain the smooth operation of the Clarity relational database.
Instructions
DO NOT query the Clarity database between midnight (12:00 a.m.) and 6:00am EST/EDT
It is imperative that you DO NOT query the Clarity database between these specific hours. This window of time is reserved to ensure daily Clarity ETL processing can run uninterrupted. In addition, querying the database during this period could produce inaccurate results.
Be aware that Clarity data may be up to 24 hours behind real-time
Clarity data is updated daily through Clarity ETL processes; therefore, data in Clarity can be up to 24 hours behind real-time.
Understand Clarity ETL processing and environments
Your Clarity account automatically provides you with access to MICPR (Production) and MICQR (QA) environments. If you need access to the development (MICDR) or testing (MICTR) environments, you must specifically request access to these environments when you set up your account.
The following illustrates the ETL processing from Hyperspace (aka: MiChart) to Clarity, including what each environment is used for to ensure Clarity runs efficiently.
ENVIRONMENT |
PURPOSE |
COPY DOWN/REFRESH SCHEDULE |
POC/MICDR |
Initial (development) build, configuration and unit testing for projects and operational changes |
Copy down from PRD is done annually, and data is wiped out, then refreshed from Chronicles POC to MICDR |
TST/MICTR |
Integration testing for MiChart applications and associated interfaces. NOTE: Load your own test data into TST through Hyperspace |
Copy down from PRD is done annually, data is wiped out, then refreshed from Chronicles TST/MICTR |
STG/MICCR |
Final testing validation, regression, and integrated testing just before moving to PRD |
Copy down from PRD is done annually, data is wiped out, then refreshed from Chronicles STG/MICCR |
PRD/MICPR |
Live production environment – NEVER test reports or extracts in PRD |
N/A |
MICQR |
Copy of PRD/MICPR and is designed for perform testing in Clarity environment that mimics production |
Refreshed weekly on Friday evenings starting at 5 PM IMPORTANT: The refresh can take up to five hours to complete; any custom-created objects from your schemas will be overwritten during this time.
NOTE: Your access to this environment will not begin until after the first scheduled refresh date following the date you received your Clarity account |
DVRFUL/MICER |
Used for projects or longer-term development efforts |
A copy down from PRD is done twice a year, including the patient data
|
More information about Caboodle can be found at: Caboodle Overview
Clarity notifications
As a Clarity user, you will receive notifications from the MiChart-Clarity-Developers email group. Be sure to review these notifications for updates regarding regular Clarity processing.
Problems with your Clarity account?
If you encounter any issues with your Clarity account and cannot resolve them:
- Contact the Help Desk at Ext. 68000.
OR
- Submit a Request for Help (Level-2 credentials required) through the IT Service Catalog. In the Additional Information field, indicate that the request should go to the MiChart Cogito Administration group.
Post-Upgrade Considerations for New Clarity Users:
After upgrades or ad-hoc changes to the Clarity data model, Clarity users should be prepared to investigate table/column deprecations and to wait for backfills to complete. For more information on these upgrade follow-up processes, see: Clarity Data - Post-Upgrade Reminders for New Users.
Need additional assistance?
If you require additional assistance, post-upgrade, regarding deprecated or backfilled tables and columns, please submit a ticket to the HITS ServiceDesk. Request the ticket to be routed to the MiChart Cogito Administration assignment group.