The scope and purpose of these maps is unclear to the uninitiated reader. Both the descriptions and the naming conventions could use some work. Meanwhile, perhaps some language about the maturity of this asset would be helpful. 

"cm" seems to stand for "canonical map". It includes maps from FHIR to V2 and V3. 

The main table lists V2/V3 as source, FHIR as target, but the maps themselves go the other way.

"sc" seems to mean "status code", which is redundant with most if not all of the names (e.g., sc-care-team-status). It seems to mean maps from FHIR resource-bound value sets to pattern-defined values. 

The relationship between "cm" and "sc" is not clear. The "sc" maps seem more "canonical" than the "cm" maps.

The one V2 map seems problematic. "ADT_A04.DG1" cannot be "equivalent to" three disjoint FHIR values.

Naming proposal: [source]to[target]-[concept]
cm-address-type-v3 => fhir-to-v3-address-type
sc-appointmentstatus => fhir-to-pattern-appointment-status