When messages need responses — and those responses need to be tracked, assigned, and rerouted — use the FHIR Task resource alongside Communication. This separates message content (Communication) from the routing and assignment lifecycle (Task), allowing you to reassign work without modifying conversation data.
The patient submitted their intake form — now what? This page covers the patterns for triggering intake processing and the workflows that follow once intake data has been ingested into FHIR resources.
How you track sent, received, and read for messages depends on two things: whether a message can have more than one recipient (group threads), and whether you need to search for unread messages via the API. Use the decision guide below to choose the right model.