GithubHelp home page GithubHelp logo

adhocteam / coverage-validator Goto Github PK

View Code? Open in Web Editor NEW
1.0 1.0 5.0 28.49 MB

Interactive form and web service for validating QHP, provider, and drug JSON documents

Home Page: https://qhp-validator.herokuapp.com/

HTML 26.22% Go 66.28% Makefile 6.72% Shell 0.79%

coverage-validator's People

Contributors

christophermanning avatar gcs272 avatar greggersh avatar isawpalmetto avatar kingishb avatar mrleebo avatar paulsmith avatar sethetter avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

coverage-validator's Issues

2017 Changes: Is specialty actually a required field for groups?

Hi there!

According to the specification at
https://github.com/CMSgov/QHP-provider-formulary-APIs/tree/2017-changes#user-content-schema-1 the group type does not have any remarks about specialty being a required field. In fact it does not have any specialty field defined whatsoever.

The schema/2017 branch validates groups with a required specialty field, which makes sense to me but I can't find any other artifacts/information supporting this interpretation of the spec.

Can someone clarify if it's correct to interpret specialty as required for groups?

Relevant issue in the QHP repo:
CMSgov/QHP-provider-formulary-APIs#27

Enforce NPI types

NPI type 1 -> INDIVIDUAL
NPI type 2 -> GROUP + FACILITY

Requires NPPES database

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.