Comment:

If CIMI is to provide a semantic underpinning for FHIR resources, it would be optimal for the resources (or profiles) to carry the explicit semantic bindings of the elements intended. The SD seems to provide two options for doing so: the Code property and the Mapping property. It should be clarified which property is intended for such use, and, if it may also be intended for other uses, it would be best to provide a relationship property specifying what the external code is intended for (e.g., 'normative semantic definition of property with respect to its resource,' or 'requirements tracing to statutory billing identifier').

Summary:

Are semantics of an element from code or mapping?