Medplum React overrides for Observation lookups in...
# support
n
Hello Medplum team, We are working off a fork of the medplum-scheduling repo and are trying to connect references of Observations onto a Goal resource for a Patient. However our clinicians find it difficult to use the lookup input field as our users have several Observation resources each varying with different dates which stem from the same CodeSystem defined from its ObservationDefinition, which are not exactly specified in the UI (see image). Additionally in order for any result to show up, they have to type in the exact name of the Code - We've tried workarounds to override some of the components with not much luck; is there a clear way to override these React components, particularly the query it is using to fetch the dropdown items? I want to add that I often come across friction with the pre-existing React components which I have to implement overrides for - if there is a set way to implement such overrides or define our own components that would be great!
r
HI @nebbishy thanks for the thoughtful question. I'm very impressed with how far you've gotten with the existing componetns
I'm sorry you're encountering friction with our existing components. We view them primarily as tools for "rapid prototyping" to get started, but most users tend to create their own components once they build more custom experiences
> define our own components that would be great You're always welcome to write your own React components! However, there isn't a way to drop them into
app.medplum.com
> lookup input field as our users have several Observation resources Unfortunately we don't have solution for this today , but this couldmake a good Prop to our existing component
We're happy to accept a Github Issue, or even a PR if you're willing
182 Views