The InterSystems EHR Reports Specialist exam is designed to validate core skills for specialists who design, set up, and support InterSystems Reports within InterSystems EHR.
Number of questions: 50 Exam time limit: 1.5 hours Passing score: 74% Language offered: English Exam format: Multiple choice and multiple response
Exam Topics and Content
The exam contains question items that cover the areas for the stated role as shown in the KSA (Knowledge, Skills, Abilities) chart immediately below. All questions are based on Logi Report Designer V19.
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 Creates InterSystems Reports using Logi Report Designer within InterSystems EHR
T1.1 Describes what the specification is saying
Recalls what data sources and procedures are, and how to access the sources of data
Identifies what parameters are used from the specification
Distinguishes between different page report component types (e.g., cross tabs, banded objects, normal tables)
T1.2 Identifies the components of InterSystems Reports
Distinguishes between catalogues and reports
Recalls the features of a catalogue
Catalogues connections and terms
Accesses the catalogue manager in the designer
Identifies which data source types are used in reporting
Identifies the data source connection and how to modify it
Identify what is required to use a JDBC connection
Recalls what a stored procedure is
Recalls when and why to update a stored procedure
Distinguishes between different data sources and their use cases
Recalls the importance of binding parameters
Manages catalogues using reference entities
Recalls how to change the SQL type of a database field (e.g., dates)
Identifies how to reuse sub-reports
Recalls the different use cases for sub-reports
Describes how to use parameters within a sub-report
Recalls how to configure the parameters that the sub-report requires
Recalls how to link a field on a row to filter sub-reports
Recalls the potential impact of updating stored procedures on the settings
T1.3 Uses Logi Report Designer to design and present data
Distinguishes between the different formats of reports
Determines when and how to use different kinds of page report component types
Recalls the meaning of each band and where they appear (e.g., page header vs. banded page header)
Recalls how to add groups and work with single vs. multiple groups
Differentiate between the types of summaries
Uses tools to manage, organize, and group data and pages, including effectively using page breaks
Identifies when to use formulas
Uses formulas to format data and tables
Determines how to best work with images, including using dynamic images
Uses sub-reports effectively
Inserts standard page headers and footers into reports
Recalls how to embed fonts into reports
Applies correct formatting, localization, and languages
T2 Integrates InterSystems reporting within InterSystems EHR
T2.1 Understands InterSystems EHR report architecture
Recalls how to set up a report manager entry
Recalls how many user-inputted parameters can be used in InterSystems EHR
Recalls how to set up menus for a report and how to add menus to a header
Recalls what a security group is and adds menus to security group access
Configures InterSystems EHR layout webcommon.report
Differentiates between different types of layout fields
T3 Supports InterSystems Reports
T3.1 Verifies printing setup
Debug using the menu or preview button
Tests the report by making sure it runs as expected
Demonstrates how to run reports with different combinations of parameters
Tests report performance with a big data set
Identifies error types
T3.2 Uses print history
Identifies use cases for the print history feature
Recalls the steps to retry printing after a failed attempt
Uses print history to verify parameters are correctly passed to the parameters in the stored procedure.
Recalls how to identify a report was successfully previewed or if it encountered errors