@wyclif, @dkayiwa, and I discussed this ticket and have a relatively quick fix – i.e., avoid using collection setters on domain objects; rather, use add/remove methods. Doing this in the REST API will avoid the error caused by the change in the underlying collection type in Platform 2.0 (patient identifiers were sorted, but not implemented as an ordered set until Platform 2.0).