@mindbill/angular 0.12.0 → 0.13.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -0
- package/fesm2022/mindbill-angular.mjs +1816 -1669
- package/fesm2022/mindbill-angular.mjs.map +1 -1
- package/package.json +2 -2
- package/types/mindbill-angular.d.ts +184 -172
package/README.md
CHANGED
|
@@ -81,6 +81,15 @@ rejection = {
|
|
|
81
81
|
|
|
82
82
|
The component falls back to the legacy singular `reason` and `code` fields when `issues` is absent. Set `appearance.dangerColor` to customize its red treatment.
|
|
83
83
|
|
|
84
|
+
When MindBill authorizes **Correct and resubmit**, the lifecycle component
|
|
85
|
+
opens the same complete `MindBillBillSubmissionComponent` used for the first
|
|
86
|
+
submission. It carries forward the immutable snapshot and authenticated
|
|
87
|
+
document copies, highlights controls named by rejection `fieldPaths`, keeps
|
|
88
|
+
payer contact guidance visible, and submits the corrected bill and documents
|
|
89
|
+
as a new immutable attempt. The canonical `billId` stays the same and every
|
|
90
|
+
attempt remains in the bill history; the Angular host does not need a custom
|
|
91
|
+
correction form or resubmission API adapter.
|
|
92
|
+
|
|
84
93
|
Procedure codes, modifiers, and rendering taxonomy all use the same styled searchable dropdown (`mindbill-combo-box`) with code + description rows, hover states, and typed custom-code entry for complete CPT/HCPCS/medical-legal codes. Service lines accept multiple modifiers rendered as removable chips. PDFs can be dropped anywhere on the screen — a full-page overlay confirms the drop target — with the same 25 MB per-file, 100 MB total, and 20-document limits as the React form.
|
|
85
94
|
|
|
86
95
|
The default reference directories and field rules live in the component library. Hosts can provide custom procedure, modifier, and taxonomy options without reimplementing the form. For a fixture or Storybook, pass an async `submitter`; omit it in production so the component talks directly to the Partner API.
|