Hello, Medplum Team! I have some questions regarding the way

Extensions

,

Profiles

,

StructureDefinitions

, and

ImplementationGuides

are used in Medplum. Based on the Profiling section of the Docs (https://www.medplum.com/docs/fhir-datastore/profiles), I see that Medplum supports the addition of new

StructureDefinitions

and a reference via the

meta.profile

which will allow for validation on save as well as ability to search based on

meta.profile

. What is unclear though is how/if we can leverage these changes to the underlying data model in Medplum for Querying and working with data beyond this. Below are a couple of questions in this area: 1. Can the

MedplumClient

be updated to use newly defined search parameters on a FHIR Resource defined in a Profile? If so, does this work for both existing FHIR Elements and added Extensions? 2. Is there any way to update the

@medplum/fhirtypes

library to support newly added Extensions, search params, and/or updated cardinality? I realize that this package is managed by Medplum, but could we update the

@medplum/definitions

or and build a forked version of

@medplum/fhirtypes

based on this or something similar? 3. Is it possible to apply a Profile (via

StructureDefinition

in the Medplum Project) so that it applies to every instance of a Resource, or is it only enforced with the canonical reference at the individual Resource level? Happy to answer any follow-ups or clarify as needed. Still new to FHIR Profiling/Extensibility so please correct if anything is misstated in the above. Any additional documentation you may have is appreciated as well.

1) Extensions are not currently searchable even if they exist in the profile 2) This is at present a limitation 3) At present only enforced with the canonical reference at the individual resource level