Combined resolution with  FHIR-42847 : Fix technical formatting issue with the example snippet update section: https://hl7.org/fhir/us/core/general-requirements.html#claiming-conformance-to-a-us-core-profile Claiming conformance to a US Core Profile A conformant server: SHALL  Be able to populate all profile data elements that are mandatory and/or flagged as Must Support as defined by that profile’s StructureDefinition. SHALL   SHOULD declare conformance with the US Core Server Capability Statement  by including its official URL in the server’s  CapabilityStatement.instantiates  element:  http://hl7.org/fhir/us/core/CapabilityStatement/us-core-server SHALL  specify the full capability details from the US Core CapabilityStatement it claims to implement. Declare support for the US Core Profile by including its official URL in the server’s  CapabilityStatement.rest.resource.supportedProfile  element the US Core Profile’s official or “canonical” URL is located on each US Core Profile page Declare support for the US Core Profile’s FHIR RESTful transactions The restful transactions for the US Core Profiles are documented in the “Quick Start” section on every profile page. Example CapabilityStatement snippet for a server conforming to the US Core Patient Profile:   3. RE: The differences between Conformance language surrounding Profile + Interaction Support vs Profile only_ Support: For Profile only Support: Implementers may only need specific profiles from US Core to fulfill their use case.  They should document these dependencies and formally declare them in their CapabilityStatement as documented in the referenced section.  However, it is impractical to make this an absolute requirement for all implementations because it cannot be enforced through testing, and systems may choose not to do this for many reasons.  Therefore, the conformance verb SHOULD reflects that it is a best practice or recommendation to be considered by implementers within the context of their particular implementation.Implementers need specific profiles plus interaction defined in US Core to fulfill their use case.   In contrast to Profile only support, for  Profile + Interaction Support Implementers including those who undergo g(10) certification need specific profiles plus interaction defined in US Core to fulfill their use case. The conformance verbs SHALL reflects that this is an absolute requirement for all implementations and alerts systems that this is a testing requirement for certification. These CapabilityStatement requirements can be enforced through certification testing. Non-certified systems that choose not to do this are technically non-conformant.