September 2021
We've got some exciting things released this month! *queue the 🎉 please*
1up will do all the required payer to payer work for health plans which use our Send and Receive product “meet compliance” for the Payer to Payer Data Exchange CMS regulations that go into effect on January 1, 2022. Our solution provides a method to send data to other payers via FHIR® APIs and receive FHIR® and non FHIR® data from external health plans. For health plans using us just to meet compliance we have you covered. Learn more here.
Improvements have been made to the member authentication and consent screens to improve member experience and accessibility:
- Members will now be asked to actively check that they have read and understand the provided consent language prior to approving sharing data with a 3rd party app.
- Members will now be given the option to exit the data share process by clicking
Cancel, and will be returned to their requesting 3rd party app without authorizing data sharing. - We have resolved accessibility errors within authentication to align with guidance in Section 508 and WCAG 2.0, and we continue to evaluate and identify additional areas where accessibility can be improved.
The 1upHealth Clinical Research Connector application facilitates a provider’s ability to provide relevant patient information via the 1upHealth FHIR Platform for use in conjunction with clinical research and clinical trials. Check it out!
We have added support for FHIR Bulk $export for an entire client ID (instead of just a single oneup user as before). This allows you to easily export all of a given resource type for your entire Client ID.
curl --location --request GET 'https://analytics.{{baseUrl}}/bulk-data/r4/$export' \
--header 'client_id: xxx' \
--header 'client_secret: yyy' \
--header 'x-oneup-user-id: client'
And then to get one of the returned NDJSON bundles:
curl --location --request GET 'https://analytics.{{baseUrl}}/bulk-data/r4/$export/Patient/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdGFydCI6IjAwMDAiLCJlbmQiOiIxVFc1IiwidG90YWwiOjExNTAsInVzZXJJZCI6ImNsaWVudCJ9.RTYRDns84Sx_bia-oNi-KNKaxsJV8LcvS7TRmgHWv1E.ndjson' \
--header 'client_id: xxx' \
--header 'client_secret: yyy' \
--header 'x-oneup-user-id: client'
We fixed a bug that caused an additional unnecessary
_next link to be included when paginating through response bundle.For example using the
paging token on the Condition resource that has 30 entries, we now return 2 pages of results if we do a _count=15We have added more strict validation of dates when resources are POSTed to our FHIR server.
For example when POSTing a Patient resource, we now more strictly validate date attributes like
birthDate to ensure they are valid date types, instead of strings or other incorrect datatypes.1up connects 1000s of health facilities using FHIR. Check out the list of all the health plans (payers), health systems (providers), and other FHIR® API connections that 1upHealth has available.
Learn how 1upHealth supports CMS Rule Requirements here: https://1up.health/products/cms-rule/technical-requirements
Checkout our CEO, Ricky Sahu, on CommonWell TV TV discussing the ONC information blocking regulation, and the future of healthcare IT. Watch now!
The 1upHealth App Gallery is a central home for FHIR interoperable apps. We're excited to add:
Last modified 1yr ago