Motion to find not persuasive as the mappings are meant to be from the v2 standard to the FHIR standard.  It uses the FHIR messaging context to ensure that all elements of a v2 message are able to be addressed where the receiver of the v2-FHIR mapping bundle determines whether to progress with a FHIR message, set of FHIR REST API interactions, store it in FHIR resource format, etc., etc.  We note that FHIR does not imply a transaction/interaction method, whether message, REST, or otherwise (e.g., a FHIR bundle inside a Direct message).  Rather FHIR is a data format standard that can be used in many different exchange and access paradigms.  Thus, naming it v2-FHIR Messaging would be limiting.  While many equate FHIR to RESTful API implementations only, that represents an incorrect understanding of the FHIR standard.  It supports RESTful APIs, but is not limited to it.