KSA Group
|
KSA
|
Target Item
|
- Demonstrates mastery of foundational concepts required for TrakCare integrations
|
1. Accesses TrakCare system and locates test patients and data
|
- Describes components on the EPR
- Explains how Edition provides region-specific functionality
- Uses TrakCare to perform patient and episode lookup, and to perform other basic operations
|
|
2. Examines and configures basic TrakCare settings
|
- Describes important items in the Configuration Manager (e.g. Site Code, System Paths, etc.)
- Identifies steps to configure integration-related code tables
- Toggles TrakCare features
|
|
3. Examines and interprets TrakCare data model and data definitions, and performs basic SQL queries
|
- Examines and interprets data definitions and relationships between tables using TrakCare Data Dictionary UI
- Examines and interprets data definitions, relationships, and global storages with InterSystems class reference function
- Performs basic SQL queries on patient, episode, and order items
|
|
4. Examines and interprets integration security configuration settings
|
- Describes TrakCare application security model
- Examines security settings using the Management Portal in InterSystems IRIS
|
|
5. Interprets HL7 V2 requirements
|
- Describes common HL7 V2 message types (e.g., ADT, SIU, REF, and ORM/ORU)
- Correlates TrakCare triggering events with HL7 V2 message types
- Describes mapping between HL7 V2 data and TrakCare data model
|
|
6. Interprets HL7 FHIR requirements
|
- Names common HL7 FHIR resources
- Correlates HL7 FHIR resources with TrakCare data model
|
|
7. Identifies elements in an SDA
|
- Identifies important elements within SDA structure
- Examines SDA definition by using the InterSystems class reference guide
- Correlates SDA elements with HL7 V2 message segments and fields
|
2. Uses the HealthCare Messaging Framework (HMF) for TrakCare integrations
|
1. Demonstrates mastery of foundational HMF concepts
|
- Uses the HMF (TrakCare/SDA3) Clinical Summary
- Uses the HMF External Search and Merge workflow
- Uses the HMF FHIR Manager
|
|
2. Designs and configures HMF productions
|
- Identifies steps to define and configure HMF according to the integration solution design/architecture
- Examines existing HMF configuration settings
- Lists roles of each generated production (System, Router, Gateway)
- Prepares HMF productions and interfaces according to the integration solution design
|
|
3. Develops and customizes HMF productions
|
- Formulates development and customization plans
- Develops custom inbound/outbound methods
- Enhances generated DTL code
- Creates extensions
- Enables/disables Event Triggers/productions using Integration Manager
- Configures Outbound Query interfaces and makes process calls to search patient information from an external system.
- Creates additional SDA elements (extensions) at container and patient levels
|
|
4. Deploys HMF solutions
|
- Prepares HMF adapter-based productions and interfaces
- Contrasts local versus remote deployments
|
|
5. Manages and monitors HMF productions
|
- Examines integration events and SDA content using Integration History UI
- Views configuration settings (e.g., ports, URLs, file paths, etc.) for business services and business processes generated in each production (System, Router, and Gateway)
- Identifies production status using the Production Manager and InterSystems IRIS Message Viewer
- Examines message workflow using Visual Trace in the InterSystems IRIS Management Portal for each production
|
|
6. Troubleshoots HMF productions
|
- Examines and interprets low-level HMF trace details in ^zTRAK("HMF") global
- Examines HMF production settings
- Formulates resolution strategies
|
3. Configures TrakCare for external access and access to 3rd party applications
|
1. Configures inbound data access
|
- Uses external SQL tools (e.g., WinSQL to perform SQL queries)
|
|
2. Configures outbound data access
|
- Creates and runs SQL queries against external tables or views
|
|
3. Uses SOAP web services
|
- Writes InterSystems ObjectScript code to invoke external SOAP web services
- Uses SOAP Wizard to create proxy clients
- Uses industry-standard tools such as SoapUI, Postman, and CURL to make SOAP calls to TrakCare
|
|
4. Links to External Viewer
|
- Configures External Viewer for TrakCare to launch into external PACS
- Associates External Viewer to receiving location
|
|
5. Launches into 3rd party application with context
|
- Names TrakCare in-process variables
- Creates and configures custom charts
|
|
6. Uses TrakCare REST APIs
|
- Retrieves TrakCare API Swagger documentation
- Configures TrakCare REST APIs using the API Manager
- Audits REST API history
|