Page:  
Jun
16

Creating Custom Applications on Verify My Identity

Not only is Verify My Identity is a fully customizable Identity Provider, but you can now build your own custom application or applications right on top! Verify My Identity takes care of all the user account management stuff, so you don’t have to. All you need to do is build your own application in Django, make a few settings and voilà, you have your application running. Creating applications this way is huge time saver. We often help our clients build custom applications on top of Verify My Identity.

Verify My Identity can be used in standalone mode or in conjunction with multiple “upstream” Identity Providers such as Okta or Google. Verify My Identity can be hosted by Videntity as a service or you can run it in your environment such as Amazon AWS or Microsoft Azure.

Call or email us to setup a demonstration. We can be reached at +1 888.871.1017 or sales@videntity.com.

Jun
16

Videntity adds support a verifiable vaccine credential to Verify My Identity

Verify My Identity now has the ability to add a verifiable credential of vaccination such as COVID-19. Using the SMART Health Card technical specification, Verify My Identity allows users to download a special QR code containing name, date of birth, a vaccination details. These QR codes can be printed on paper or stored digitally. If your organization is a government entity or a source of truth for vaccination records call or email us to setup a demonstration. We can be reached at +1 888.871.1017 or sales@videntity.com.

Aug
11

CMS Rule Help: State API Implementation Playbook

We’ve published some help for states implementing the new CMS Interoperability and Patient Access Rule.

Let Videntity help you do this the right way.

https://bit.ly/state-api-playbook

Sep
4

Videntity is Awarded a Major Contract to Support Consumer Direct Exchange for Medical Members

The Alliance for Better Health has awarded Videntity a contract to build the nation’s first consumer-directed health information exchange supporting Medicaid members in New York. Building off our work on the Blue Button 2.0 for the Centers for Medicare and Medicaid Services , we are creating a truly transformational service that intersects identity and healthcare. We are honored and and humbled to be working with the Alliance for Better Health on this impactful endeavor.

For the official announcement, please see https://abhealth.us/press-release/regional-consumer-directed-health-information-exchange/. For even more details see http://www.docnotes.net/2018/07/cdex.html.

Jun
12

What is the difference between “FHIR Bulk Data” and “flat FHIR”?

What is the difference between “FHIR Bulk Data” and “Flat FHIR”? They are different names for the same thing! http://blog.transparenthealth.org/2018/06/fhir-bulk-api-aka-flat-fhir.html

#HealthIT #FHIR

Nov
14

Announcing the DJmongo Amazon Machine Image (AMI)

We’ve made it much easier to get going with Djmongo by using a pre-built Amazon Machine Image (AMI). Here is a link to kick off your very own instance in Amazon Web Services Elastic Cloud Computing (EC2).



ami-27164930

Notes

The size of the instance you’ll need will be based on your data. We recommend an M3- XLarge for medium sized applications. Be sure to open port 80 (HTTP) when setting up security groups After the instance is fully launched, point your browser to the instance’s public DNS. The default console username/password is kitty/purry.

Nov
12

Be Your Own DJ Winner Announced

Please congratulate Molly Gehring for trying out Djmongo during All Things Open 2016. Molly is a developer at the Office of Research Informatics at the Duke University School of Medicine. She won the records player and 3 vinyl albums from our booth. Way to go Molly!

Oct
24

Be Your Own DJ: Build an API and Win

Create an API with Djmongo for a chance to win a new turntable and 3 Vinyl Records!

You don’t have to use the Amazon Machine Image (AMI), but it is highly recommended that you do because it will get you up and running quickly. Here is a link to kick off your very own instance in Amazon Web Services Elastic Cloud Computing (EC2).



ami-27164930

The size of the instance you’ll need will be based on your data. We recommend an M3- XLarge for medium sized applications. Be sure to open port 80 (HTTP) when setting up security groups After the instance is fully launched, point your browser to the instance’s public DNS. The default console username/password is kitty/purry.

Rules

  • * You must be an attendee at the 2016 All Things Open Conference
  • * Submit the URL of the API and what it does to sales@videntity.com by 4PM on October 28 2016.
  • * The winner will be determined by the Videntity team

The winner will be announced here on this blog and on Twitter by 5PM on Thursday October 28 2016. We welcome any feedback you have on Djmongo as well.



Good Luck!

Aug
10

Getting Quality-based Payment Models Right Means Replacing X12

Check out our guest blog post on quality-based payment models and the X12 standard:

Getting Quality-based Payment Models Right Means Replacing X12 on the Zansor’s blog.

Apr
22

The Medicare Provider Directory API

The Centers for Medicare and Medicaid (CMS) recently released Medicare provider enrollment data contained in the “Provider Enrollment, Chain, and Ownership System” or “PECOS”. CMS will release updates of these new public data about every quarter. The Medicare Enrollment data are useful because not only because they show if a provider participates in Medicare, but also organizational affiliations. For example, doctor A serves Medicare patients at hospital X and clinic Y. At clinic Y, doctors that take Medicare are doctors A, B, C, etc. This kind of information is useful to state Medicaid agencies, health plans, and the general public. This article explains how I created an API out of this public data.

Background on the Data Format

You can read all about the data here but the short version is that is the data are divided into three flat files: a base file containing basic demographic information, an (incomplete) address file, , and a reassignment file. In Medicare/PECOS terms, a reassignment is when a health provider reassigns the benefit to another party. Often practitioners are not paid by Medicare directly, but instead opt to “reassign” the benefit to an organization, such as a hospital, which is often where the provider receives his or her salary. This reassignment is indicative of an affiliation or work relationship.

Processing the Data

To make the PECOS data more accessible, the three flat files must be transformed. I first converted the three flat files into three MongoDB collections using the command-line utility “csv2mongo.py” found in  json-data-tools. After I indexed certain fields for speed, I wrote a custom script to sort through the data and yield two new MongoDB collections called “combined_organizations” and “combined_individuals”. Then using the RESTful API framework Djmongo as the RESTful Application server responsible for exposing the new data, voilà, I have a functioning RESTful API for Medicare providers. All the input required is the NPI number for the organization or individual in the URL.

Using the API

As an example, we can determine that “Leslie Crytser”, with the NPI of 1205824083, is enrolled with Medicare with two organizations, “Stony Point Surgery Center, LLC”, and “West End Anesthesia Group”. Here is an example using Leslie’s NPI:

https://djmongo.oauth2.io/search/api/public/pecos/compiled/compiled.json?npi=1205824083

And on the flip side, we can see which providers are setup to bill Medicare through a particular institution such as, “Stony Point Surgery Center, LLC”, with the NPI of 1255498457, using the following RESTful URL:

https://djmongo.oauth2.io/search/api/public/pecos/compiled/compiled.json?npi=1255498457

Summary

While functional, this PECOS API is still a work in progress. I plan to add address data and convert the documents into proper  FHIR resources. Currently, the address data only contain city, state, and zip code. I hope CMS decides to release the address line information in the future. After some further updates, I plan to make available the script that creates these files possibly within the Provider Data Tools package or elsewhere.

A final item to note is that just because a provider/institution is included in the PECOS data, doesn’t necessarily mean that any services were provided via Medicare. PECOS enrollments/re-enrollments work on a 5-year schedule; therefore the provider/institution may not currently be accepting Medicare patients.

I hope the health information ecosystem finds this somewhat useful. Feedback welcome.

Page: