# Release Notes ## 26.04.2 ### Enhancements * A footer has been added to the 1up Console with the version number, a link to create a support ticket, and a link to the 1up Security Trust Center. ### Bug fixes * The API Usage Reports graphs in the 1up Console were rendering multiple times. The API Usage Reports graphs now only render once. * The 1up Console would display an error message for customer environments without data to populate the API Usage Reports graphs. Customers without data now see an empty graph instead of an error message. ## 26.04 ### Enhancements * The 1up Console now contains a Member Data Sharing page under Reporting that displays information about members who have opted in to Payer-to-Payer Data Exchange. * Member Data Sharing includes a list of opted-in members, the external payer they requested send data, and whether that data has been received. * The FHIR Resources page is no longer available in the 1up Console. * A notification has been added to Patient Viewer in the 1up Console when an error occurs and data cannot be displayed. * A configurable logo has been added to the Payer-to-Payer opt-in pages. Payer provide 1up with the logo image to use. * Partial match logic has been added to the Payer-to-Payer opt-in pages when searching for health plans. * Updated description for the Manually Submit Health Plan page to no longer reference uploading a driver's license. ## 26.03.2 ### Enhancements * A notification has been added to API Usage Reporting in the 1up Console for when an error occurs and data cannot be displayed. * The 1upHealth Help Center link in the Payer to Payer member opt-in User Interface (UI) directs to the Payer to Payer section of the Help Center. * Patient Access is now supported for customers using the 1upHealth Multi-Tenant Environment. * Provider Access now has an opt-out process for members. Payers can choose to integrate 1up with their Identity Provider (IdP) or use a 1up provided non-IdP process to verify member identity. Payers can also choose to provide 1up with opt-out data resulting from their own process instead of using one provided by 1up. See [Setup member opt-out process with IdP](/docs/provider-access/opt-out) and [Educational materials for members](/docs/provider-access/member-education) for more information. * Payer-to-Payer Data Exchange now has an opt-in process for members. Payers can choose to integrate 1up with their Identity Provider (IdP) or use a 1up provided non-IdP process to verify member identity. Payers can also choose to provide 1up with opt-in data resulting from their own process instead of using one provided by 1up. See [Setup member opt-in process with IdP](/docs/payer-to-payer/opt-in) and [Letter to members template](/docs/provider-access/template-member-letter) for more information. ### Bug fixes * The Export button in the 1up Console failed to export data if the customer did not have their data mapping completed. This issue has been resolved. The Export button exports unmapped data when available. ## 26.03 ### Enhancements * The Resources page in the 1up Console has been updated with recent webinars. * The UAT environment of the 1up Console has been updated with a banner identifying it as a non-production environment. * Exported files from the 1up Console have contextually relevant names. * The Help button in the 1up Console has been updated to direct to the 1up Platform Help instead of the 1up Help Center. * Queries to the Provider Access API can now return data from multiple sources for the same patient. Each data source in a response is separated into different Patient resources. * Example: A provider uses the Provider Access API to $export a patient's data from their health plan. That patient has opted-in to 1up's Payer to Payer Data Exchange so their current health plan has data from two previous payers. The provider's response includes three Patient resources — one for each data source (health plan). ### Bug fixes * The Patient access tab under API Usage Reports in the 1up Console was not clearing selected filters when the user switched to another tab. This issue has been resolved. The Patient access filters are cleared when the user switches to another tab, such as Provider directory. * The Providers page under Network Connections in the 1up Console was not displaying all of the options in the user menu. This issue has been resolved. All pages in the 1up Console display the same options in the user menu. ## 26.02.2 ### Enhancements * An Export button has been added to API Usage Reporting in the 1up Console. * Export is available in the Patient access tab. * Patient access API usage reports can be exported in the CSV or XLSX format. * The Resources page in the 1up Console has been updated with recent webinars. ## 24.12 ### Enhancements * Revised the current list of approved third-party applications. * 1upHealth has implemented a weekly internal process to verify the status of all of our existing Patient Connect clinical EHR endpoints (for example, check if the Mayo Clinic Patient Connect endpoint login page loads properly). This process has uncovered 681 clinical patient-mediated endpoints that were deleted from the list of Supported Health Plans & Health Systems. This process provides 1upHealth more real time insights when an endpoint is broken so 1up can troubleshoot the problem proactively. * Since June 2024, 1upHealth has added 109 new clinical patient-mediated endpoints and updated the vast majority of our EHR endpoints from DSTU2 to R4 (customers who will only need to support the latest R4 version). This expansion eases the burden on 1up's Support team who currently field a variety of requests related to legacy versions. ## 24.10 ### Enhancements * Added a new Get Admin System Search endpoint to the current 1up System Search API. * Added a new Get Zip Code System Search endpoint to the current 1up System Search API. * Added a new Patient Connect OnDemand Ingest API endpoint which will work in hand with 1up's Refresh Token Service. * Added a new Patient Connect Get Token Status API endpoint which will work in hand with 1up's Refresh Token Service. * Added a new Patient Connect Post Revoke Data Access API endpoint which will work in hand with 1up's Refresh Token Service. ## 24.08 ### Enhancements * Improved security for the System Search IFrame. * Standard security reviews for the release related to the 1up Platform and features in this release: Group Bulk Export and System Search IFrame. * Support for subdividing client IDs using FHIR Group resources. This includes an improved authorization process. * Support for bulk export operations at the group ID level using the client ID. * Population-level support for the Group Bulk Export feature. * Support for resolving URN placeholder ID references in POST transaction bundles to the correct resource ID. ### Bug fixes * Fixed an error that caused the Aetna logo to be mapped to the wrong payer-to-payer auth page. * Fixed an error that blocked filtering of System Search query results by FhirVersion. Customers can now filter results by FHIR version. ## 24.05 ### Enhancements * SQL on FHIR on Redshift is now generally available. SQL on FHIR on Athena has been deprecated. * Minor technology enhancements. * The Provider Search API, Provider Search tool, and Health History now return search results in alphabetical order. * Upgraded Epic Patient Connect endpoints to support R4 ingestion. * Added new endpoints for these payers to Health History: * Cascade Comprehensive Care, Inc. * Empower Healthcare Solutions, LLC * Sendero Health Plan * The Health Plan of West Virginia, Inc. * Resolved a problem with the Humana payer endpoint to enable payer-to-payer ingestion. * Architectural enhancements to capture more robust file attributes for customer environments. * Architectural enhancements to capture more robust file metadata for customer environments. * Updated the supporting services for the 1up FHIR Server. * Customers can now export read-only population-level data using the 1up FHIR API * Implemented improvements to speed and reliability. Bulk Export jobs now run in the order that they were created. ### Bug fixes * Fixed an error that caused improper AuditEvents recording before sending outbound data. ## 23.10 ### Enhancements * Single-tenant environments using FHIR R4 can now use the asynchronous Purge operation. This enables the 1up FHIR Server to better handle deleting data with larger data sets. * This release adds a new endpoint to connect to at the end of the Purge operation, and modifies some aspects of the workflow. This new, asynchronous workflow enables you to seamlessly delete data and minimizes timeouts. * Single-tenant environments using FHIR R4 can now use the asynchronous Export operation. This enables the 1up FHIR Server to better handle deleting data with larger data sets. This version also includes a Group Export function. * This release adds a new endpoint to connect to at the end of the Export operation and modifies some aspects of the workflow. This new, asynchronous workflow enables you to share large amounts of data faster. It provides better scalability and handles larger data sets. It also supports exports at the group or population level. * This updated, robust CCDA to FHIR conversion service is integrated with the standard ingestion workflow, and includes a data contract-based validation service to verify the data quality of the ingested CCDA data. This broadens the ingestion funnel and enables us to accept clinical data from 1up customers. * This updated, robust HL7v2 to FHIR conversion service is integrated with the standard ingestion workflow, and includes a data contract-based validation service to verify the data quality of the ingested HL7v2 data. It also includes mapping templates based on v2.5.1 This broadens the ingestion funnel and enables us to accept clinical data from 1up customers. * 1up Population Connect now supports patient list CSV files of up to 200,000 patients for Epic® sites. * 1up Patient Connect now includes 763 production Veradigm endpoints for the 1up patient-mediated network. This expands the network of providers that’s available to our 1up Patient Connect Digital Health customers. * 1up Patient Connect now includes six new connections for the 1up payer network, which increases the ability of members to share data from their previous plans. * New connections include: AIDS Healthcare Foundation, Mass General Brigham Health Plan, Fallon Health, Maryland Physicians Care, AultCare, and BlueCross BlueShield of Nebraska. * Improvements to Provider Search for multi-word queries. * This change enables users to more easily search for and find the supported providers in the 1upHealth provider network.