INTERSYSTEMS LEARNING SERVICESInterSystems Change Control

InterSystems Change ControlConfidential - Do Not Duplicate

COPYRIGHT NOTICE© 2020 InterSystems Corporation, Cambridge, MA. All rights reserved.
InterSystems is a registered trademark of InterSystems Corporation.

InterSystems, InterSystems Caché, InterSystems Ensemble, InterSystems HealthShare, HealthShare, InterSystems TrakCare,TrakCare, InterSystems DeepSee, and DeepSee are registered trademarks of InterSystems Corporation.

InterSystems IRIS data platform, InterSystems IRIS for Health, InterSystems IRIS, InterSystems iKnow, Zen, and Caché Server Pages
are trademarks of InterSystems Corporation.
All other brand or product names used herein are trademarks or registered trademarks of their respective companies or organizations.
This document contains trade secret and confidential information which is the property of InterSystems Corporation, One MemorialDrive, Cambridge, MA 02142, or its affiliates, and is furnished for the sole purpose of the operation and maintenance of the products ofInterSystems Corporation. No part of this publication is to be used for any other purpose, and this publication is not to be reproduced,
copied, disclosed, transmitted, stored in a retrieval system or translated into any human or computer language, in any form, by anymeans, in whole or in part, without the express prior written consent of InterSystems Corporation.
The copying, use and disposition of this document and the software programs described herein is prohibited except to the limited extent
set forth in the standard software license agreement(s) of InterSystems Corporation covering such programs and related
documentation. InterSystems Corporation makes no representations and warranties concerning such software programs other thanthose set forth in such standard software license agreement(s). In addition, the liability of InterSystems Corporation for any losses ordamages relating to or arising out of the use of such software programs is limited in the manner set forth in such standard software
license agreement(s).
THE FOREGOING IS A GENERAL SUMMARY OF THE RESTRICTIONS AND LIMITATIONS IMPOSED BY INTERSYSTEMSCORPORATION ON THE USE OF, AND LIABILITY ARISING FROM, ITS COMPUTER SOFTWARE. FOR COMPLETE
INFORMATION REFERENCE SHOULD BE MADE TO THE STANDARD SOFTWARE LICENSE AGREEMENT(S) OF
INTERSYSTEMS CORPORATION, COPIES OF WHICH WILL BE MADE AVAILABLE UPON REQUEST.
InterSystems Corporation disclaims responsibility for errors which may appear in this document, and it reserves the right, in its sole
discretion and without notice, to make substitutions and modifications in the products and practices described in this document.
For Support questions about any InterSystems products, contact:
InterSystems WorldWide Response Center
Telephone: +1-617-621-0700
Tel: +44 (0) 844 854 2917
Email: support@InterSystems.com

Confidential - Do Not Duplicate

ICC 540: CCR Tier 1 –InterSystems HealthShare®

0 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

Objectives
 Identify subtleties for using change control for HealthShare.
 Demonstrate best practices for using CCR for HealthSharechanges.
 Identify how secondary environments are used in the CCR
workflow.

1 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

Best Practices
 Use Tier 0 CCRs when not feasible to maintain item in source
control.
 Makes change discoverable.
 Enforces workflow such as peer reviews.

 Use source control when possible.
 Tier 1 CCR with ImplementCCR routine.

 Goal from product management: Increase range of changes covered by source control.
 Increase ease of use of source control across the full range ofproducts.
2 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

Part 1: CCR for HealthShare Components

3 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare: All Products HealthShare built on InterSystems IRIS.
 Anything that applied to InterSystems IRIS applies to HealthShare.
 Customizing productions same as customizing productions for InterSystems
IRIS.

 Complex object synchronization framework.
 Only use supported APIs.
 Search documentation for components with export and import methods.

 Many components do not even support using SQL on tables.
 Do not directly change globals.

4 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

Challenge for Source Control
 A lot of configuration contained in rows of tables.
 HealthShare configuration tables do not support CCR.
 Cannot export row from BASE and submit to a CCR for progression
to all Environments.

 Goal from product management to support maintaining
HealthShare configuration in source control.

5 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare Health Connect
 Many additional components candidates for Tier 0 CCR only: Facility Registry.
 HealthShare Service Registry.
 OID Registry.
 Assigning Authority Registry.
 Configuration Registry.
 XUA Configuration Registry.
 Coded Entry Registry.
 Exclude Audit Events table.
 FHIR CSP Configuration.
6 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare Unified Care Record: Candidates forTier 0 Only
 Everything in Health Connect.
 User/Clinician Registry.
 Gateways Registry.
 Consent Registry (multiple tables).
 Program Registry.
 Relationship Registry.
 Clinician Group Registry.
 PIX Notification Registry.

7 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare Unified Care Record: Candidates forTier 0 Only (cont.)
 Query Instance Registry.
 Security Domains.
 Consent Groups.
 Push Notification settings (Delivery Management).
 Terminology settings (multiple tables).

8 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare Unified Care RecordRecommendations
 Separate CCR Systems for Edge Gateway, Access Gateway,Registry and ODS.
 Also use separate CCR System for HSCUSTOM namespace.
 Use secondary Environments for multiple gateways.

 Custom Management Reports edited using Tier 1 process inIDE.
 Create web application definitions to allow IDE access toitems in filesystem not available elsewhere.
 Examples: /csp/xslt and /distlib

9 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

Secondary Environments
 Additional environments to receive changes at same time ascorresponding primary environment.
 Any primary environment can have 1+ secondary environments.

 Secondary environments for BASE require deployment ofItemSet during In_BASE state.
 See ICC440 for more information.

10 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare Secondary Edge Gateways
Repo

E1E2

Repo

11 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

E1E2

Repo

E1E2

HealthShare Health Insight Use Analytics Management Portal source control hooks.
 Use CCR Event Handler to automatically import components
not covered by hooks.
 Use documented APIs.
 Search documentation for “Packaging Business Intelligence Elements
into Classes”.

12 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare Personal Community
 Configuration spread out across multiple external files andtables that can’t export.
 For external files, use IDE to add to source control.

13 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare Patient Index
 Export rules and thresholds using documented APIs.

14 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

HealthShare Patient Index: Linkage Definitions
 Maintain linkage definition class in source control using IDE.
 Follow procedure described in ICC530 for no portal hooks but
editable in IDE.

 Do not add generated classes to source control.
 Will be regenerated on compilation.

 Consider configuring CCR Event Handler to handle additional
required implementation steps:
 Stop production.
 Compile linkage definition.
 Start production.
 Rebuild linkage data.

15 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2

Summary What are the key points for this module?

16 | InterSystems Change Control | CCR Tier 1 – HealthShare | ICC540 v3.2