Agree with Diego. FHIR logical models are essentially clinical requirements documents, although they use basic FHIR structures and datatypes, these are not implementable FHIR artefacts. Someone has to actively choose the correct FHIR resources/profiles, which as you recognise is the hard part.
Nevertheless there is merit in using openEHR tooling and templates to develop FHIR logical models, particularly if these can auto-gnerated from templates, which Diego has shown can be done. @heatherleslie was involved in work in Australia which used openEHR methodology and tooling to create templates which were then handed over tot he FHIR technical people to decide on the appropriate resources and profiles. The advantage for us in openEHR is that our work clinical y and technically is finished when we have the template - no need for further engineering.
This becomes most obvious when we move out of FHIR’s comfort zone into detailed Care pathway datasets where right now openEHR has a whole bunch of concrete models e.g the recent Ceilings of Treatment archetype which are likely to be represented in FHIR as questionaire resources. That might be fine for exchange but it really does not support app building adequately.
And, of course we can autogenerate Questionnaire bundles from templates too.