It sounds like we should mostly leave it up to individual distributions on how they want to group encounters, I think we should make EMR API a required (instead of optional) dependency of the O3 patient chart, and adopt the /emrapi/encounter endpoint wherever we create encounters. From talking to @samuel34, we plan to eventually move hard-coded patient chart workspaces (vitals, visit notes, orders) to using the form engine, so we should focus on adopting the API for form-engine forms.