pas-metrics: bump to 0.1.6, note what metric 4 can and cannot see - #32
Merged
Conversation
0.1.6 is published to payerbox-public; point the download link, the file:// install example and the bootstrap coordinate at it. 0.1.6 fixes metric 4 to count exchanges rather than service items, so the percentage no longer skews with item count. Also adds the caveat readers keep hitting: metric 4 counts entries in ClaimResponse.error, and a submission rejected up front (e.g. by profile validation) is never stored, so it lands in neither the numerator nor the denominator.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Points the PAS Metrics page at 0.1.6, now published to
payerbox-public, and adds one caveat about metric 4.file://install example and theBOX_BOOTSTRAP_FHIR_PACKAGEScoordinate →0.1.6Why
0.1.6 fixes metric 4. Both sides of its fraction used to count rows of the metric model — and a row is a service item, not a submission — so the percentage skewed with item count (one errored three-item claim read as "100% of 3 exchanges"). It now counts distinct exchanges, matching metric 8.
The new caveat covers the question that keeps coming up: metric 4 counts entries in
ClaimResponse.error(typically an X12 error code written back by the UM system). A submission rejected up front — profile validation, for instance — is answered with anOperationOutcomeand never stored, so it appears in neither the numerator nor the denominator. Without that, people try to exercise metric 4 by sending a bad payload and see nothing move.Verification
The artifact is live and matches the repo build:
https://storage.googleapis.com/payerbox-public/io.healthsamurai.pas-metrics-0.1.6.tar.gzreturns 200, sha2568a63f6ad…equals the tarball onprior-authmain, and it unpacks as0.1.6withr4.coreas its only dependency. 0.1.4 and 0.1.5 stay in the bucket untouched.