Thoughts on structuring Reference Application "App" documentation

[Craig A.]

Hi Everyone,

I'm working on the documentation for the new manageapps feature of the Reference Application. It seems to me that it would be appropriate to structure the documentation in a "Reference Application: Apps" hierarchy. The challenge I face is that users would want a "human identifiable" way of adding/modifying an app. For example, a user may want to toggle the manualIdentifier override in the registrationapp. They would likely search "manually enter patient identifier in register a patient" instead of registrationapp.registerPatient. Should the hierarchy be structured by capability (register a patient, vitals, active visits, etc)? How do you recommend we structure the documentation?

Sincerely,

Craig