Provider ID to Organization Mapping

this mapping is done through the surescripts directories implementation using organization directory entries and mapping the relevant providers location records to these organization entries, to create an efficient and scalable solution for identifying the correct surescripts provider identifier (spi) to organization(s) important it is essential to review and understand the surescripts directories implementation guide for all the necessary details of how directory messaging functions organization location records a participant/subparticipant must create general organization location records for practices that are going to be enabled for qhin/interconnect services depending on participant/subparticipant’s system and mechanism for organizing providers, it may be easier or more appropriate to represent organization records at a more granular level follow the surescripts directories implementation guide for the full messaging specification and general organization message elements provider location records a participant/subparticipant must create provider location records for providers at each of these organizations that will be enabled for qhin/interconnect services successful addition of these records will create a unique surescripts provider identifier (spi) follow the surescripts directories implementation guide for the full messaging specification and provider message elements mapping provider to organization location records this organizationid is a critical component to the mapping process and needs to be retained by the system in association with the corresponding location record that was used to create the general organization record unique provider locations, represented as spis in the provider directory, must be updated with the relevant organizationid for the general organization this id is populated in the practicelocation > identification > organizationid field of the provider messages refer to the provider message element details section of the surescripts directories implementation guide for more information regarding this update important each spi record can only be attached to a single organization record; however, organizations may be structured hierarchically through the parentorganizationalid described in the directory implementation guide