See gForge ticket 20863 for a comment on the need for the Referral Request Transaction page (http://hl7.org/fhir/us/bser/2019May/ReferralRequestTransaction.html). But personally, I miss the sliced support bundle profiles. I think it is helpful for implementers to know what sort of observations different use cases require. I understand if you don't want to be too prescriptive, but some guidance on whether or not things like vital signs and results (A1c results, allergies, blood pressure, etc) should only be the latest and greatest values or if a series of historical values (the last 3 A1c values, etc) may be necessary in some cases. This also impacts the need for Observation based profiles to contain a dataAbsentReason element (this logically only make sense which a particular type of sliced resource is required in a bundle (as opposed to just omitting the sliced resource if there is no data to send)). At least some textual guidance on what sliced bundles may or may not include would be helpful to implementers.