InbasketRegistryConfiguration
In Basket Registries store information to determine the recipients who can display and handle specific types of messages. This table contains the basic information about these Registries. Registries are stored in the HIP master file.
| Column Name | Type | Description |
|---|---|---|
| UseCalculatedPoolManagerFlag | VARCHAR | If item 20411 has a value of no, the contents of item 20410 will not be used or updated when determining the users managers have access to. Otherwise, item 20410 will be used. |
| RegistryRecordStatus | INTEGER | This is used to store record status |
| InbasketRegistryName | VARCHAR | The name of the In Basket registry in the HIP master file. |
| UseExternalEmailItem | VARCHAR | If this registry can be used to route messages to an external e-mail address this item stores the item in the "Message Received by" master file that indicates whether messages should be sent to an external e-mail address. |
| PoolMailSystemSetting | INTEGER | This setting determines how messages are sent to this pool. If the members of this pool work with In Basket, then they should use In Basket to receive messages. If messages should be routed to an external mail system for this pool, enter External Mail and fill in the External Address item. If this pool should not receive messages, enter No Mail. NOTE: Choosing No Mail will block messages from going to this pool. In some cases the sender will not be notified. Setting this to No Mail will not block the member's access to messages sent to a pool or a workstation. For example, use this setting during a roll out for those members in clinics not yet up. If left blank, messages will be routed to In Basket. |
| DefaultAsPoolIndicator | VARCHAR | Registries can be used to define a distribution list from which you can choose one or more recipients. In this case each recipient must individually take action to remove a message from his or her In Basket. Enter No(2) to set up a Registry of this type. Registries can also be used to define an exact "Pool" of recipients, each of whom always receives a message sent to that registry. In this case, however, only one of the recipients need take action for a message to be removed from all recipients' In Baskets. Enter Yes(1) to set up a Registry of this type. If you are setting up a Pool, Selection Values are required. |
| LimitReceivableMessageTypesIndicator | VARCHAR | Specify the type of access a pool will have. This setting is used to determine the message types a pool can receive. |
| LogicalDeploymentOwnerIdentifier | VARCHAR | ID of the logical deployment owner for this record. Logical owners show the deployment where the record was created but doesn't represent if the record is a part of version skew. |
| InvalidRegistryIdentifier | VARCHAR | If an invalid pool was the reason pool is unable to recieve a message, this item will tell you which HIP was invalid. |
| PrimaryPoolManagerUserId | VARCHAR | Item 20414 in the Registry master file will allow manual configuration of the primary manager of a pool. It will store the user ID of the primary manager. It will be configured by administrators. |
| RegistryIdentifier | NUMERIC | The Registration Identification Number |
| ExternalMailAccountName | VARCHAR | External account is used only when the Mail System prompt is set to "External Mail". This setting indicates that mail generated in your licensed applications shall be routed to an external mail system. The account name to route messages to is stored here. The format of a mail account using SMTP/POP services is name@companyname.com |
| MessageSendingSystemIdentifier | NUMERIC | If the Mail System prompt is set to "External Mail" this is where the external system service (LPP record) to be used to route messages to an external account is stored. |
| RegistryClassSelectionItem | VARCHAR | If your Registry is not a pool, you can simplify selection of groups of recipients by defining classes. To do so, select an item within the "Send Message to" master file (preferably a category list). You can then choose to send a message to individuals, or to classes made up of all the individuals who have a common value for the specified Class Selection Item. |
| IsSharedInProviderDirectory | VARCHAR | Whether this should be shared in the provider directory |
| ExternalPopAccountPasswordItem | VARCHAR | If this registry can be used to poll messages from an external POP server, this column stores the item in the "Message Received by" master file that indicates the password of the POP account. |
| CategorySelectionItem | VARCHAR | This item is where you can optionally restrict selection of recipients to groups. To do so, select an item within the "Send Message to" master file (preferably a category list). This makes it so that you can no longer send messages to individuals; you can only send messages to groups made up of all the individuals who have common values for the specified Selection Item. |
| RegistryDescriptionText | VARCHAR | This is a description of the Registry. It may include information about how the Registry is set up to determine recipients and how it is to be used. |
| IsRxRefillRequestPool | VARCHAR | Pool can be used as a Rx Refill pool, which can receive Rx Refill request In Basket message from pharmacy. If set "Yes", this pool can used to set provider's Rx Refill pool in SER masterfile. The default is "No." |
| ProviderDirectorySharedName | VARCHAR | Name shared in provider directory |
| ExternalAddressItem | VARCHAR | If this registry can be used to route messages to an external e-mail address, this column stores the item in the "Message Received by" master file that indicates the e-mail address to which external messages should be sent. |
| ExternalPoolIdentifier | VARCHAR | CE external pool ID for HIP record in provider directory. |
| ReasonPoolCannotReceiveMessage | INTEGER | If the pool is unable to receive any IB messages, this item will give information on why that is the case. It is mainly for administrators to understand the problem with the pool build. |
| SelectionLinkerIdentification | NUMERIC | This item allows you to specify the Selection Linker (a programming point) to be used to make the connection between the "Send Message to" master file and the "Message Received by" master file. The STANDARD SELECTION LINKER (2700) connects User, Provider, and Department to User; Workstation to Workstation; and Patient to Patient |
| DistributionSchemeIdentifier | NUMERIC | Store the distribution scheme this pool routes to |
| PoolMessageRoutingLogic | INTEGER | Determines how messages sent to the pool should be routed. The default value is "Pool only". |
| ExternalMailStructureIdentification | NUMERIC | This is the programming point to be used to format a message routed to an external e-mail address. |
| PagerServiceTypeItem | VARCHAR | If this registry can be used to send messages to the pagers, this column stores the item in the "Message Received by" master file that indicates the type of the service used by the pager. |
| LimitCalculatedMessageTypesIndicator | VARCHAR | Only applies if HIP item 20501 is set to 0 - No or blank. Should all message types be allowed or should the pool only be allowed to receive messages of specific types. Provide a value of 1 - Yes to limit to a specific list of message types in item 20610. Leave blank or set to 0 - No to not limit the message types that this pool can receive messages for. |
| RecipientSelectionInitialValue | VARCHAR | Stores whether recipients are chosen from the User (EMP), Provider (SER), Department (DEP), Workstation (LWS) or Patient (EPT) master files. Note: other master files may be used in special cases. |
| PhysicalDeploymentOwnerIdentification | VARCHAR | ID of the physical deployment owner for this record. Physical owners will be where the data is hosted, either on the cross-over server or the owner deployment. |
| PoolDirectAddress | VARCHAR | Mixed case Direct address for this pool |