Will add a foot-note at the bottom of the table that explains why some of the exchange patterns (documents, operations & messaging) are prefixed with FHIR, while others are not. Specifically, the notion of operations, documents and messaging have existing traditional use in the HL7 space outside of FHIR and using non-prefixed terms might suggest that the guidance provided here extends to all use of these exchange approaches, as opposed to being limited to FHIR-specific exchanges.  However, the scope of this document is very much FHIR-specific.  Considerations around the use of messaging with v2 or v3 or documents with v3/CDA may be similar, but there will be differences specific to those technologies that are not addressed in this specification.