Overview of Technology by Design Systems

Request access here: Tech by Design Access Request Form

Systems

At a high level, here is an overview of the different systems which exist in the Technology by Design ecosystem.

• GitHub
  • This is the code and documentation library, but there are a few DIFFERENT libraires (e.g. Repositories) which exists under the Tech by Design organization
  • These are broken down between two Tech by Design projects - 1115 and Fusion - and are labeled as such on the request form (linked above)
  • Repositories:
    • Help Desk:
      • Shared between both projects
      • If issues arise which need attention, issues (e.g. tickets) can be opened here for follow up by the TxD team
      • QE users who will be logging, managing, or need to be aware of status of Help Desk tickets should request access to this repo
    • 1115 Hub:
      • Specific to the 1115 project - this handles HRSN traffic to the state Data Lake
      • Access can be granted to two environments
    • QE BridgeLink repository:
      • Specific to the Fusion project
      • These are QE specific repositories created for handling development and code tracking between environments (DEV/QA/PRD) for each QE’s BL instance
      • QE Integration engineers, PMs, and project sponsors should request access to this repository for management and tracking of channel development activities
    • Fusion planning repository:
      • This is where requirements and decisions related to the implementation of the Fusion project are documented
      • QE PMs and project sponsors should request access to this repository
  • In order to be provisioned with access to a repository, a user must have gone through the steps of setting up a individual GitHub account. To complete this setup, please visit this link.
• BridgeLink *
  • Transformation tool that moves data from inbound sources into the database
  • There are various instances/environments which exist under Tech by Design, so when requesting access for this, it is imperative to specify what instance and environment you are requesting access to. For example: RRHIO DEV, etc.
  • There are different environments a user can be provisioned with access to - DEV / QA / PROD
    • QA and PROD are connected to HealthShare
    • DEV is not connected to HealthShare
  • QE integration engineers will need access to the various environments for channel development, validation, and management activities
    • No offshore resources will be given access to QA or PROD
  • An overview of available environments can be found here.
• Enlighten
  • Enlighten is TxD’s tool for monitoring channels once they are live
  • Anyone who needs to manage/monitor channels would need access
• InterSystems: Management Portal
  • This is essentially the backend of HealthShare and is limited to technical resources only
  • This is where resources will have to access to look at message error logs, manage clinicians, manage patient cohorts and subscriptions for alerts, etc.
  • There are different environments a user can be provisioned with access to - BASE / LIVE (which includes UAT and PRD)
    • This setup is more involved and will require additional documentation and sign off
• InterSystems: iService Portal
  • This is the HealthShare support portal
  • Only TxD employees and our contractors need access to that
  • This is where TxD log tickets with InterSystems when the QEs notify us of HealthShare issues that need to be addressed
• Fusion Gateway User Portal
  • Fusion Gateway is the Identity Platform used for the Fusion product
  • This is where most users will be provisioned with access to access the main offerings in Fusion (including the HealthShare Clinical Viewer)
  • There are different environments a user can be provisioned with access to - DEV / QA / PROD
    • Note that Fusion Gateway will only connect to the same comparable environment of another platform
    • For example: BL QA is connected to Fusion Gateway QA; BL QA cannot be accessed through Fusion Gateway PROD
  • QE staff users will need access to the appropriate Fusion Gateway environment to access the necessary applications connected to that environment via SSO
  • Fusion Gateway provides SSO access to the following systems:
    • InterSystems HealthShare:
      • e.g. Clinical Viewer
      • This is role / consent moderated
      • Users can be provisioned for QA (UAT) / PROD (LIVE)
        • QE staff users can be given access to HealthShare Clinical Viewer LIVE for issue troubleshooting
        • QE Staff users can be given access to HealthShare Clinical Viewer UAT for channel development testing and validation activities
        • *Participant users will be given access to this portal by QE staff users when provisioned appropriately, according to QE requirements
    • BridgeLink SSO access*:
      • Same description as above
      • Eventually all access to BL will be via this SSO process and the above will go away
    • MaxMD, User Portal:
      • HISP - secure mail
      • This is for access to actual mail boxes where users will be logging in to review mail sent to them
      • There are two different environments a user can be provisioned with access to - EVAL / LIVE
        • QE staff users can be provisioned with access to EVAL for testing purposes
        • Participant users and QE staff users with mailboxes will be provisioned with access to LIVE
    • MaxMD, Admin Portal:
      • This is limited to users who will be managing user setup and maintenance (i.e. T-Users)
      • There are two different environments a user can be provisioned with access to - EVAL / LIVE
        • This setup is more involved and will require additional involvement from MaxMD
    • MaxMD, Provisioning Tool:
      • This is the where users will be managing user setup and maintenance, and is limited to users who’s job role requires them to have this access
      • There are two different environments a user can be provisioned with access to - EVAL / LIVE
        • This setup is more involved and will require additional involvement from MaxMD
• Fusion Gateway Admin Portal
  • This is where the setup and management of users and their application registrations (e.g. badges) occurs
  • There are different environments a user can be provisioned with access to - DEV / QA / PROD
    • QE users who need to manage QE staff access to QA will need access
    • QE users who will be managing QE staff and Participant Users will need access to PROD
• Verato Support Portal
  • This is where support issues which need to be escalated to Verato get opened
  • Only TxD Help Desk users have access to this portal
• Verato: UI
  • This is where QE staff will go to review / manage patient queues
  • There are different environments a user can be provisioned with access to - Dev / TEST / PROD
    • QE users who will be managing stewardship of MPI tasks will need access
    • TEST access is used for testing processes
    • PROD is used for managing production tasks on LIVE data
• Nexus Data Store
  • This is where the raw and transformed messages inbound to Fusion are stored for QEs to access as needed
  • Users needing to reprocess messages into BridgeLink will need access