Restore patient portal coverage and organize API reference by functionality - #2
Merged
Merged
Conversation
jcmrgo
changed the title
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
2 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.
Restore the 13 patient portal operations already shared with customers through Postman and organize the complete API reference by functionality. Patients, Appointments, and Clinical records come first; Catalogs comes last. Patient portal appears only in the API reference. Replace Core API/ERP/source-file groupings and generic “API Reference” children with functional sections for clinical records, charges/invoicing, inventory, telehealth, accounts, webhooks, and sites.
Companion upstream review: https://github.com/ecaresoft/nimbo-api/pull/115. Review/merge the upstream audience correction before this consumer update.
Import the committed public artifact from nimbo-api revision
34f84cd24473c8e0a120253266aee10ead32f789. Publish 11 reviewed patient reads; retain two sanitized customer OTP definitions because replacement authentication fidelity is incomplete. The six additional canonical portal operations stay excluded. Record the publication evidence and the explicit retained-inventory addition from 83 to 85 operations.The served reference contains 111 unique operations, each assigned once in navigation. Preserve existing endpoint URLs, including explicit MDX wrappers for the two waiting-room pages whose generated names otherwise collide. Trim accidental whitespace from one historical rendered path key without changing the input inventory. Preserve the reference-only host/playground, patient token security, and synthetic examples. Fix byte comparisons so UTF-8 schema descriptions do not falsely report generated-file drift.
Validation: 14 tests / 9,119 assertions passed; Mintlify validation, broken links, deterministic sync check, and diff check passed. Landing and generated endpoint inspected in light and dark mode, with the new navigation verified. Upstream API full CI passed. Merging the connected branch can publish the site; this PR is not merged.