Develop #897
Merged
Develop #897
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* providing a schema fix for the 'both' enum to support the billing_class * version bump * Update ruby.yml
Fixing documentation.
…ma. This documentation was previously included, but was removed during the v2.0 merge. (#846)
* Documentation Fix (#847) * updating table-of-contents documentation to match what is in the schema. This documentation was previously included, but was removed during the v2.0 merge. (#846) * version bump * relaxing restrictions for the allow-amount file to remain empty if there is nothing to report. * removing old examples not relevant to 2.0 updates.
…n_id_type vaues EIN and HIOS (#892) * README lower-case EIN and HIOS for in-network rates schema - Change plan_id_type values "EIN" and "HIOS" to lower case to be consistent with schema, Table of Contents, etc. #891 - Change type-o "tas" to "tax" in the Tax Identification object reference (#tas-identifier-object) * plan_id_type "EIN", "HIOS" in Readme should be lower case. Validator failure.Update allowed values in README for plan_id_type. Out of Network Out of Network Allowed Amount change, see in-network description here #891
…es and capitalization consistencies (#895) * updating documentation with the removal of external provider references and capitalization consistencies * updating test cases to be more explicit
…#889) * Fix validator issues with ein and service_code and oneOf:,const:, if: Disallow CSTM-00 with POS codes Constrain valid EIN values Fix issue with missing anchor on the ein/tin validation pattern * Fix indentation in negotiated_price service_code * Fix JSON indentation & formatting in in-network-rates.json * Allow NPI Field to be [0] (a single entry containing zero) To handle : https://github.com/CMSgov/price-transparency-guide/tree/master/schemas/in-network-rates#additional-notes "In contractual arrangements that are only made at the TIN level, where NPIs are unknown or otherwise unavailable, the value "0" should be reported for the NPI field." This change does not permit a "0" value in the Tax "Tax Identifier Object's when type is "npi". Because npi does not require business name, I propose allowing a "0" type "ein" in the unusual scenario where a provider only has an SSN, along with requiring the business name. I posted an issue regarding this scenario here : #890 (comment) Tests are failing because they are out of date. Once merged, I'll fix whatever conflicts may result.
tdfow
reviewed
Jan 9, 2026
Contributor
There was a problem hiding this comment.
@shaselton-usds @shaselton
The example that is to represent no NPI is no longer representing no NPI. It has an NPI. The name should be renamed to what it is representing.
Also with the change updated, it seems we can't include the scenario where the billing provider who has an SSN and no NPI will be published, as the changes were made to only accept the tin npi scenario as a 10 digit NPI and not the single 0.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.