With the increasing burden of technical engagement resulting from the incredible expectations generated by FHIR globally, perhaps the clinical content specification should be outsourced to... the clinicians first of all, ensuring that the clinical content can be represented in a technical format for implementation.
It certainly helps to be a clinician, although recent work on development of clinical content specifications for a Hearing Health application has taken me further into modelling for the range of audiometry, 226Hz and high frequency tympanometry, audiology speech testing, and hearing screening than I’d ever imagined. Modelling the raw data capture (or downloaded from devices) for these tests is really quite simple, but enabling the complexity of different states, events and protocols that reflect audiological practice has been much more complex than I anticipated. I attempted to model these some years ago, based on my (obviously rather poor) research on the web at the time. Take a look at my meagre effort to build the original archetype for Audiogram Result (as built by a GP who has never performed an audiogram).
See the full detail here - http://www.openehr.org/ckm/#showArchetype_1013.1.44_1
And the most recent archetype as designed and verified by practising grassroots Audiologists… I didn’t even get the name of the concept correct!
See the full detail here - http://dcm.nehta.org.au/ckm/#showArchetype_1013.1.1097
Identifying domain experts for the development and then collaboration on verification/validation of each type of archetype/template is absolutely critical for success.