HealthShare Unified Care Record Technical Specialist - Retired

The HealthShare Unified Care Record Technical Specialist exam is designed to validate core skills for technical professionals who implement, extend and manage all aspects of HealthShare Unified Care Record.

An IT implementation professional who:

• Leads the technical implementation of HealthShare Unified Care Record based on requirements generated by the system design by the project’s technical architect

• One completed HealthShare Unified Care Record implementation, version 15.x - 2022.x
• Basic proficiency with ObjectScript
• Experience with HealthConnect interfacing
  

• Classroom courses:
  
  • HealthShare Unified Care Record Fundamentals (5 days)
  • Building and Managing HL7 Integrations (5 days)
• Online learning resources:
  
  • Integration Architecture (course, 30m)
  • HL7 V2 Business Services and Business Operations (course, 30m)
  • Searching Messages Using the Message Viewer (course, 1h 30m)
  • Delivering Timely Healthcare Messages with Unified Care Record (learning path, 1h 30m)
  • Introduction to the Clinical Viewer (course, 30m)
  • Data Orchestration and Management in Unified Care Record (learning path, 10h)
• Review the following related content in HealthShare Documentation:
  
  • Deploying Unified Care Record Instances
  • Unified Care Record Upgrade Guide
  • Translating Terminology in Unified Care Record
  • Clinical Viewer
  • Unified Care Record Consent Guide
• Review the set of practice questions

Number of questions: 76

Exam time limit: 2 hours

Passing score: 63%

Language offered: English

The exam contains question items that cover the areas for the stated role as shown in the KSA (Knowledge, Skills, Abilities) chart immediately below. The question items are presented in two formats: multiple choice and multiple response.

TOPIC/KNOWLEDGE	SECTION/SKILLS	ABILITIES
T9 Installs Unified Care Record	T9.1 Makes pre-installation decisions based on technical architecture document	Interprets solution architecture document; Identifies connectivity options for data receipt
	T9.2 Installs software and Unified Care Record components	Installs software and license key to target environments; Installs Unified Care Record components with wizards; Activates Unified Care Record components
	T9.3 Performs post-installation configuration	Configures production components; Configures external communication; Selects pool sizes for production components; Starts and stops Unified Care Record; Configures MPI connectivity
	T9.4 Upgrades existing installation	Prepares Edge gateways for upgrade; Upgrades Productions with Installer: Access, Edge, Registry; Confirms upgrade in log files; Reactivates productions; Preserves custom code and layouts
T10 Implements Unified Care Record	T10.1 Implements consent policy decisions	Configures consent policies – system, facility, and patient; Configures consent groups; Assigns users to consent groups; Configures clinical information qualifiers, types and rules; Configures consent options
	T10.2 Implements Clinical Message Delivery	Creates delivery filters, options, relationships and transformations; Enrolls clinicians; Creates subscriptions; Determines subscription basis; Creates dynamic cohorts1; Creates custom report(s) with patient data
	T10.3 Implements IHE	Enables and configures IHE production components; Tests IHE connections with IHE test utility; Transforms CDA data to support IHE
T11 Extends and Customizes Unified Care Record	T11.1 Configures Unified Care Record data feeds	Implements prebuilt adapters or custom business components for messaging; Creates routing rules; Defines data transformations; Creates custom DTL and business host pipelines; Uses HealthShare customization coding best practices; Adds Message Routers; Configures services for message routing
	T11.2 Extends SDA for custom data elements	Extends existing SDA objects via extension classes; Creates custom SDA containers and streamlets
	T11.3 Customizes terminology	Loads code sets; Adds default code set for incoming data; Creates/Loads a terminology translation map; Sets up code registry; Creates code system profiles; Specifies default coding systems – Access Gateway transforms; Configures terminology translation
	T11.4 Customizes clinical user interfaces2	Customizes patient search page; Customizes Clinical Viewers, including chartbooks, charts, chart items, and patient banners; Adds custom SDA object as a field in a chart; Customizes Clinical Navigation display; Describes what customizations can be done using CSS vs. ISC tools
T12 Administers Unified Care Record	T12.1 Manages reporting	Uses Management Reports; Builds custom reports
	T12.2 Manages registries	Views Gateway Registry; Views/Adds to Facility Registry; Views/Adds to Assigning Authority Registry; Manages cohorts in Cohort Registry3; Views/Adds Service Registry; Views/Adds/Edits Configuration Registry
	T12.3 Manages users and roles	Defines users, roles and privileges; Uses pre-defined roles; Creates custom roles; Manages access to patient data via roles/policies; Implements federated authentication and authentication domains; Manages users
T13 Supports Unified Care Record	T13.1 Traces patient data flow through productions	Sends sample data to Unified Care Record; Identifies key production components in data flow; Uses Visual Trace for troubleshooting; Investigates missing data
	T13.2 Interprets messaging through productions	Identifies key messages in data flow; Determines troubleshooting entry point when message tracing; Identifies custom vs. standard code; Identifies custom code that should not be present
	T13.3 Uses tools for troubleshooting	Interprets event log entries; Interprets alert messages; Uses Production Monitor for troubleshooting; Uses business rule log

¹ In versions 2019.1 and higher, smart programs have been renamed to dynamic cohorts.
² Both v1 Clinical Viewer and v2 Clinical Viewer (introduced 2018.1) and their respective tools are covered in this exam.
³ In versions 2019.1 and higher, program groups and Program Registry have been renamed to cohorts and Cohort Registry respectively.