Q: Who do I contact to learn more about the process and benefits of this transition?
A: There are many ways you can stay informed about the transition process:
WISHIN will conduct a series of webinars and training sessions providing more detail and insight into WISHIN 2.0.
There will also be a section of the monthly newsletter dedicated to the transition. Participants can also contact us at firstname.lastname@example.org to schedule time to speak with the WISHIN team.
Q: Can I just start the process without attending one of the webinars?
A: WISHIN strongly recommends attending one of the webinars that will be scheduled in the coming months. However, if no one from your organization is able to attend, we can work with your organization individually to walk you through everything you need to know. To discuss further, send us an email at email@example.com.
Q: Will my access to WISHIN Pulse change during the transition?
A: No. Webinars and training sessions will be available that will describe the changes, enhancements, and benefits of WISHIN 2.0. We will also notify you when the current WISHIN Pulse system will transition to the new platform.
Q: How would I access WISHIN Pulse after the transition?
A: WISHIN Pulse can be accessed via web portal. Users must have a valid username and password. There is no need to know where the patient had previous encounters. All that is needed is the patient name, and, if known, other demographic information. For a brief description and demonstration of the new WISHIN Pulse system, click here.
Q: Will my Single Sign-on (SSO) change?
A: Organizations leveraging SSO will be required to make some changes as the encrypted keys to the new system must be issued.
Q: What is the timing of this transition?
A: WISHIN has begun transition work with both Velatura and KPI Ninja. We anticipate that the transition will be complete on or around September 30, 2021.
Q: Is real-time pharmacy data available in WISHIN Pulse?
A: Medicaid and health plan PBM data is available. WISHIN does not yet have pharmacy data from hospital or independent pharmacies themselves. WISHIN will continue its outreach to Walgreens, CVS, hospitals, and other pharmacies to contribute this data. WISHIN looks forward to partnering with our participants to bring in these sources of data.
Q: What is the source of SDOH data coming from?
A: Today SDOH data exists within the ADT feeds through ICD-10 and Z-codes, additionally there is social determinants data in CCDAs contributed to WISHIN that we will now be able to parse. WISHIN is also looking at partnerships with SDOH-specific organizations to create bi-directional integrations.
Q: How will Population Health analytics be available?
A: Pop-health analytics will be accessible through WISHIN Pulse and online solution. WISHIN will also be positioned to integrate pop-health analytics and dashboard in a participant organization system, EHR, or EMR.
Q: How will P4P metrics shared across organizations?
A: WISHIN will be positioned to share P4P measure data at an individual-level and population-level data for QPP, MIPS, eCQM, etc. for blood pressure, A1c, mammogram, BMI, etc. More information abou the P4P MY2021 incentive program can be found here: https://www.forwardhealth.wi.gov/WIPortal/Subsystem/SW/StaticContent/Provider/medicaid/hospital/p4p_guides/pdf/MY2021_HospitalP4P_GuideV2.pdf.spage
Q: What will be expected of my organizations as part of this transition?
A: WISHIN has a plan to migrate all historical data and source contributor interfaces with minimal Participant burden. The WISHIN implementation team is working on an outreach plan to share the specifics of the work and level of involvement individually with each data contributor.
Q: What enhancements can I look forward to as part of this transition?
A: Participant access to WISHIN Pulse will not be interrupted during the transition. Webinars and training sessions will be available to describe where users will be able to find the information they’re used to viewing, and to highlight the additional benefits of WISHIN 2.0:
Compliance with ONC Information Blocking (USCDI) requirements
FHIR-enabled platform to push and pull data
Vaccinations through a WIR integration
Payer information in the encounter history
Customization of WISHIN Pulse experience
Ability to create a community (HL7 data) ingestible CCDA from WISHIN Pulse
Patient dashboard and analytics capabilities
New options for automated data delivery
Q: In the WISHIN 2.0 Community Health Record will radiology images be available?
A: The WISHIN 2.0 Community Health Record can receive images from PACS. Today, EKGs from some organizations are available in WISHIN Pulse. We plan to roll out that functionality to anyone ready to establish a gateway between WISHIN Pulse and its PACS.
Q: What organizations are participating in WISHIN?
A: More than 2,000 sites of care participate in the WISHIN HIE network in some form or fashion consisting of health systems, hospitals, clinics, correctional facilities, health plans, post-acute facilities, etc. A full list of participants can be found here - https://wishin.org/ParticipatingProviders/WISHINParticipantMap.aspx
Note: this list changes frequently
Q: Is using WISHIN HIPAA compliant?
A: Yes. Clinical information may be shared without explicit informed consent for treatment, payment, and operations purposes. WISHIN, along with all WISHIN participants, must comply with the policies, procedures, and regulations established by the Health Insurance Portability and Accountability Act of 1996 (HIPAA) as well as other applicable law. Additional information may be found here: https://wishin.org/HIE/HIEPrivacySecurity.aspx
Q: How does this model support TEFCA?
A: The Trusted Exchange Framework and Common Agreement (TEFCA) outlines a common set of principles, terms, and conditions to support the development of a Common Agreement that would help enable nationwide exchange of electronic health information (EHI) across disparate health information networks (HINs). TEFCA envisions a network of Qualified Health Information Networks (QHINs) that enable national exchange. Velatura’s sister entity, USQHIN, intends to apply to be a QHIN under the TEFCA framework. Velatura will continue to work together with WISHIN as more details related to TEFCA and QHINs unfold, providing WISHIN all information necessary to support an informed decision, including USQHIN’s full capabilities to support interstate data exchange at a national scale.
Q: How will WISHIN be able help meet ONC and CMS Interoperability Rules?
A: WISHIN has worked to establish the necessary legal framework, technical components, and connections and are primed to help our participants address these new challenges and requirements resulting from the Final Interoperability Rules. Following the transition, modular FHIR API solutions will be available to address compliance needs, while positioning your organization to advance data sharing initiatives and objectives to streamline business processes, increase care coordination, and improve outcomes for your patients/members. The infrastructure will be built to scale and address current and future interoperability needs and regulations.
WISHIN will be able to leverage its position to centralize core components of its API Platform solution to provide streamlined and cost-effective solutions. By centralizing core aspects of this solution at the WISHIN level participants will be able to:
- “Plug in” to the necessary components required to satisfy compliance requirements
- Leverage WISHIN’s centralized developer portal to manage the 3rd party apps registration and authorization process, which will improve app options for members and reduce the burden of managing app requests on organizations
- Utilize the enhanced identity and data matching and enriched data options, including clinical and provider data
- Collaborate with other WISHIN participants and existing connections to expand to other data sharing use cases by using InterOp Station as a highway to other interoperability
Q: Who can I contact if I have additional questions?
A: Please contact us by calling 608-274-1820 or emailing us at firstname.lastname@example.org