The InterSystems CCR EHR Application Specialist exam is designed to validate core skills for InterSystems EHR application specialists who use CCR to document, transport, and deploy configuration changes across environments.
Number of questions: 81 Exam time limit: 2 hours Passing score: 70% Language offered: English Exam format: Multiple choice and multiple response.
Exam Details
The exam contains question items that cover the areas for the stated role as shown in the KSA (Knowledge, Skills, Abilities) chart immediately below.
Note: InterSystems now offers two EHR products - TrakCare and IntelliCare. Both products share the same core infrastructure. Therefore, when referring to features common to both products, the term InterSystems EHR is used.
TOPIC/KNOWLEDGE
SECTION/SKILLS
ABILITIES
T1
General Concepts
T1.1
Describes basic change control concepts
Defines change control as a concept
Discusses the benefits of change control and the risks of not having it
Defines source control alone and in the context of change control
Names tips for successful use of change control
T1.2
Describes change control with InterSystems
Describes change control tools used within InterSystems including CCR and Perforce
T1.3
Describes CCR and its main concepts
Defines CCR First Principles
Identifies the workflow order between the 4 possible CCR Primary environments
Defines the term CCR system
Defines the term CCR Transport and describes the movement of changes between environments, CCR, and Perforce
Defines the terms Perforce branch, Item, and ItemSet
Describes CCR Usage Tiers and gives examples
T1.4
Performs basic tasks in CCR
Navigates the CCR homepage, main menu, and main pages
Accesses documentation and FAQs
Defines the terms State, Phase, and Transition
T2
CCR Tier 0
T2.1
Progresses a Tier 0 CCR
Defines the terms Organization, Responsible Organization, Site Code, System, and System Code
Creates a Tier 0 CCR Record
Describes use of fields available when creating a CCR
Recalls who can pass peer reviews in the CCR workflow from IN_PREP to CLOSED
Documents every state from In_PREP to Closed in a BASE-TEST-LIVE workflow including peer reviews
Selects the correct transition for deferred deployments.
Transitions CCRs to the next state
Performs the markPREPComplete transition
Identifies the workflow for failPeerReview
Performs the markAcceptanceFailed
Describes markValidationFailed transition, including best practices
Describes the importance of Peer Reviews
Describes the importance of closing CCRs
Recalls in which state an authorization is needed to progress a CCR
Implements and tests changes in correct states of the workflow
Locates and uses CCR Transition History
Identifies and uses the env token
T2.2
Uses Auxiliary Tools and Transitions
Reassigns CCRs
Describes the effect of Peer Review routing configuration options including System Architects and Default Peer Reviewers
Recalls when a CCR can and cannot be merged
Performs merge transitions and interprets results
T3
CCR Transport
T3.1
Describes CCR Transport Basics
Describes CCR Client Tools
Describes CCR Transport workflows for disconnected environments, including uploading ItemSets from BASE to CCR and deploying ItemSets from CCR to TEST/LIVE
Deploys ItemSets using best practices
Describes the automatic preview integration on passPeerReview transition
Identifies states and transitions with possible Perforce and/or ItemSet activity
Uses CCR Transport best practices including the importance of cancelling CCRs properly
T3.2
Describes CCR Transport Tools and terminology in the CCR Record
Defines the term changelist
Locates and identifies available meta data for submitted changes
Logs into Perforce in CCR
Describes diff chunks and merge conflicts
Finds and interprets list of ItemSets associated with a CCR
Defines and identifies the importance of baselining
T3.3
Describes CCR best practices and debugging techniques
Uses Catch-up CCRs
Uses the revision history
Locates and interprets error messages
Uses transport log to retrieve additional error details
Identifies cause and solution for merge conflicts
Identifies and describes how to resolve errors in bundle and upload validation
Describes options if uploaded to wrong CCR
T4
CCR Tier 2
T4.1
Uses Tier 2 CCRs to safely progress changes made in InterSystems EHR applications
Identifies when it is appropriate to create a change session in BASE
Recalls what is required in order to create a change session
Uses Change Control Menu within the InterSystems EHR side menu (bundle list)
Uses the Find GUID tool
Uses the Change Control menu to undo changes in the correct order
Uses the Change Control screen to bundle and upload changes
Identifies how security groups impact the visibility of Change Control menus
Recalls the importance of the exclusion list
Recalls how Code Table Overrides impact configuration changes
Identifies how and when to deploy ItemSets in workflow
T4.2
Recalls features of the CCR Tier 2 User Interface
Identifies whether a source control issue is related to TCC
Identifies whether a source control issue is related to CCR
Recalls the function of the GUID Prediction in the CCR UI
Recalls the importance of the "Create ItemSet" button in the Perforce Details section
Recalls when to use the "Perforce Integration" feature in the Perforce Details section
T4.3
Debugs CCR errors
Distinguishes between primary key and GUID
Recalls what ElementXML is and how to view it
Identifies scenarios where support needs to be contacted
Recalls why an ItemSet does not show up in an ItemSet list
Recalls what an Advanced reassign is
Recalls what to do when an itemset becomes stale
Recalls what to do when a token becomes invalid
Cancels and backs out of CCRs
Uses the Restore To Base flag
Resolves circular dependencies between CCRs
Resolves missing GUID errors
Identifies cause and solution for misaligned GUIDs