PHC-Hub logo  PHC Hub Administrator User Guide (v. March 2018)

WIR User Role Access and Permissions

PHC Hub limits access to various features by showing/hiding their associated menu items. Non-menu based functionality, like inbound HL7 message authentication, is also supported. Each feature is associated with one of the following modes:

The following list details WIR roles and their associated PHC Hub modes:

WIR Role PHC Hub Mode
PHC_HUB ORG LEVEL PERMISSION
  • GENERAL_MODE
  • TEST_MODE
  • REVIEW_MODE
PHC-HUB REGISTRY LEVEL PERMISSION
  • GENERAL_MODE
  • TEST_MODE
  • REVIEW_MODE
  • PROFILE_ADMINISTRATOR_MODE
PHC-HUB SITE LEVEL PERMISSION
  • GENERAL_MODE
  • TEST_MODE
  • REVIEW_MODE
PHC-HUB REGISTRY & PROJECT_TRACKER_ACCESS
  • PROJECTS_MODE
PHC-HUB UPLOAD_HL7_ACCESS PERMISSION
  • IMPORT_MODE
  • EXPORT_MODE
PHC-HUB ADMINISTRATOR PERMISSION
  • SYSTEM_ADMINISTRATOR_MODE
PHC-HUB REG_AND_UPLOAD
  • GENERAL_MODE
  • TEST_MODE
  • REVIEW_MODE
  • PROFILE_ADMINISTRATOR_MODE
  • IMPORT_MODE
  • EXPORT_MODE
PHC-HUB ALL_IN_ONE
  • GENERAL_MODE
  • TEST_MODE
  • REVIEW_MODE
  • PROFILE_ADMINISTRATOR_MODE
  • IMPORT_MODE
  • EXPORT_MODE
  • PROJECTS_MODE
  • SYSTEM_ADMINISTRATOR_MODE

Roles Associated with IMPORT_MODE

When an HL7 message is received by the PHC Hub inbound interface servlet, the application must first authenticate that the message came from a valid source and then must determine which profile to associate the message to. Each message is sent with a username and password in the HTTP transaction. PHC Hub looks to see which imMTrax organization the user is associated with and then knows what profile to use. For this strategy to work, users that are assigned to inbound HL7 interfaces must be associated with a single organization in imMTrax. If this is not the case, the message is rejected.

STC | One logo