Public health agencies and their data repositories are typically hosted and controlled by a state or government entity. Generally speaking, providers connect to public health applications using web services. The data exchanged usually includes a list of results or codes (e.g., diagnosis codes, immunizations, syndromic surveillance, electronic lab reporting, etc.) that are used for public health monitoring and reporting.
Every public health organization and application is unique, which can be especially challenging for larger providers who may need to connect to multiple states. A multi-state health system may need to connect to 12 different states, for example, and some application service providers need to connect to all 50 states. These customers have the challenge of jumping through the hoop 50 different times as each state has different requirements.
Thankfully, many reporting agencies provide sample code that aids in creating the interface. Corepoint Health has customers in every state, which has allowed our Professional Services team to compile a long list of reference implementations they can access to assist customers. Because we’ve spent the time deciphering the subtleties required to connect to state repositories across the country, we can quickly get customers connected.
Having access to this knowledge is tremendously beneficial for Corepoint customers. Having access to info, such as unique SOAP header information, can save customers time and headaches. Often, our PS team can simply share a file containing the agency’s required custom objects that can be immediately implemented in Corepoint Integration Engine. And, after a few clicks, the customer will be ready to start sending data.
Learn more about how Corepoint Integration Engine uses Web Services.Tags: population health, public health, web services