In DSTU1, FamilyHistory [1] was tied to a patient, with the resource returning an array of relatives, each with an array of problems. In DSTU2, FamilyMemberHistory is scoped to the relative level, meaning that a single resource contains problems relating to a single relative. This breaks the structure of EHR systems that model family history similar to other history information which is scoped to the patient level and without discrete modeling of relationships. Suggest that the DSTU1 model be re-adopted.