@arbaughj, I presume you’d do this via the hack that we discovered where since you can define apps (via JSON in a textarea in the admin UI) you can therefore define an empty app that has extensions in it.
Is that documented in the right place? I see System Administration: Manage Apps - Documentation - OpenMRS Wiki but I wonder if it would be better if we could get you to write a tutorial-style piece which starts out with a use case, and describes how you do it.
Thanks @darius. I’ll be happy to add some how-to use-case examples to the page you mention once I figure out how to do it myself.
I didn’t know I could create a link to something with a JSON in a texarea in the admin UI. I’ll have to give that a try. I was thinking to use the configuration for the page after HTML form submission to open my clinical summary. Or as a worst-case, really hacky way, configure an implementation defined form, with a JavaScript re-direct in it to open my clinical summary.
I was specifically thinking of writing up some examples on a shared page (similar to the form bank) for the json to configure the registration app; how to add additional person attribute fields, address hierarchy, manual identifier entry, retrospective entry, etc.