I mean that it may be good to rename “processor” to “model” and “EncounterFormProcessor” to “encouter” so that it is up to the consumer of the form to pick the exact implementation for a form modelled around “encounter”. In case of your angular formly module it will be EncounterFormProcessor, but for Android we can have EncounterFormOfflineProcessor and EncounterFormRestProcessor processors. “Model” carries a bit different meaning for the field, but it is not strictly necessary. I’m just trying to understand what Burke suggested in Abstract the Post-Form Handling and how to apply it.