Skip to content

v2.73.1 — Phase 4: monitor read-op fix

Choose a tag to compare

View all tags
@avelikiy avelikiy released this 13 Jun 14:29
v2.73.1
This tag was signed with the committer’s verified signature.
avelikiy Alex
SSH Key Fingerprint: nD9xQzAb/3YFTUEHwDpi26wMHeq89yGJsV5XW/FadYQ
Verified
Learn about vigilant mode.
b2999d2
This commit was signed with the committer’s verified signature.
avelikiy Alex
SSH Key Fingerprint: nD9xQzAb/3YFTUEHwDpi26wMHeq89yGJsV5XW/FadYQ
Verified
Learn about vigilant mode.

Systemic fix: flow steps referenced a connector by id only, so the runner defaulted to its FIRST capability — a WRITE op for write-capable connectors. 10 monitor steps were re-running the irreversible write (e.g. rcm monitor → clearinghouse:submit-837 instead of fetch-835). Idempotency guarded real double-submission, but it was semantically wrong.

  • Tools now accept explicit connector:op (backward compatible). Fixed 10 monitor steps to read ops; added check-status to irs-efile.
  • Phase 4 Wave 1 (rcm + live FHIR/EHR) verified end-to-end: live FHIR + NLM code-sets + NCCI → gate → approve → live 837 submit; irreversible write only after a signature.
  • Tests: flow-connector-ops (3); all 25 flows valid. Follow-on great_cto-nl5 for 8 pre-gate cases.
Assets 2
Loading