Add patientIdentifier and setting Parameters To fhirR4ToManifest (Python & TypeScript)

[boris-careev]

Description of Changes

• Add optional patientIdentifier parameter to ConvertFhirR4ToManifestRequest type in TypeScript
• Add optional patient_identifier parameter to fhir_r4_to_manifest method in Python
• Update parameter handling to pass patientIdentifier to the API endpoint

Issue Link

This PR addresses the following issues:

https://github.com/CareEvolution/IO/issues/387

Security

REMINDER: All file contents are public.

• I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc. Of particular note: No temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.
• My changes do not introduce any security risks, or any such risks have been properly mitigated.

Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.

Change Control Board (CCB) Approval

CCB approval is required when the change affects organizational processes (like vulnerability management or disaster recovery), or has the potential to impact availability, security, or privacy. See the CR process for more detailed assessment guidelines.

• This change does NOT require CCB approval.
• This change DOES require CCB approval. Tag @careevolution/ccb.

Testing/Validation

Describe how we will know if the change is working as intended. Consider both pre-production testing and post-implementation validation, including environment/configuration details, if applicable.

TODO: REPLACE WITH YOUR TESTING/VALIDATION PLAN

Backout Plan

Describe how we will restore the system to its pre-change state if something goes wrong.

Reverse merge-commit

Implementation Notes

Describe any special considerations for implementing the change: scheduling constraints, down-time planning, if a co-pilot is needed, etc.

TODO: REPLACE WITH IMPLEMENTATION NOTES

Documentation Updates

Describe any necessary updates. Consider both internal (wiki, checklists) and external (user guides, developer docs, customer communications) documentation.

• This change has no documentation impact.
• This change impacts external documentation (API docs, user guides). Tag @careevolution/mdhd-docs or @careevolution/api-docs.
• This change impacts internal documentation (procedures, security plans, wiki). Tag the owner.

TODO: REPLACE WITH A DESCRIPTION OF DOCUMENTATION UPDATES, if applicable

Reviewers

• I have assigned the appropriate reviewer(s).

Minimally, a second set of eyes is needed ensure no non-public information is published. Consider also including subject-matter experts and editing/style reviewers.

[bindu-careev]

    - `patient_identifier`: The identifier to use as patient.identifier in patient manifest. If this is not provided, the default identifier from the patient resource in bundle is used

[bindu-careev]

Can you please add support for a setting query parameter in this same PR?

setting: This is a pre-coordinated value to allow an API user to control manifest output in terms of the columns included in a specific manifest file or the order of the columns. If not provided, expect the default manifest output, as documented.

[bindu-careev]

@boris-careev once you add the clarification to the query param, we can get this merged.
@jeremytwfortune - will need your help on this please.

[boris-careev]

@boris-careev once you add the clarification to the query param, we can get this merged. @jeremytwfortune - will need your help on this please.

Done, waiting for your approval, @lynnfaraday, so merging is unblocked