Support bidirectional patient updates in Bridge plugin

[marythought]

Internal tracking: https://canvasmedical.atlassian.net/browse/KOALA-2895

[Copilot]

Pull Request Overview

Adds support for bidirectional sync of patient contact points and exposes a simple API endpoint for creating patients via the Bridge plugin.

• Expands RESPONDS_TO to include contact-point events and refactors compute() to handle them
• Implements get_patient_id() for resolving patient IDs from contact-point events
• Introduces BridgePatientSyncApi with a POST /routes/patients endpoint

Comments suppressed due to low confidence (3)

extensions/bridge/protocols/bridge_patient_sync.py:179

• Returning str(patient) will produce a model representation, not structured JSON. Return a dict with explicit patient fields or serialize the model to JSON.

return [ JSONResponse( content=str(patient), status_code=HTTPStatus.CREATED).apply() ]

extensions/bridge/protocols/bridge_patient_sync.py:165

• sanitize_url will throw an IndexError if url is an empty string. Consider validating input length first or using url.rstrip('/').

def sanitize_url(self, url):

extensions/bridge/protocols/bridge_patient_sync.py:169

• [nitpick] The new BridgePatientSyncApi class and its post method lack unit or integration tests. Add tests to cover valid and invalid payloads.

class BridgePatientSyncApi(SimpleAPI):

[Copilot]

Passing the ORM object contact_point directly into the JSON payload will likely fail serialization; extract only the necessary primitive fields (e.g., phone number or type) before sending.

Suggested change

	'telecom': contact_point if contact_point else None,
	'telecom': telecom,

[marythought]

replaced by #154