1. Emory Mobile App Catalog Administration Part 1: Mobile App Processes & Background

2. Agenda: Session 1 Emory Mobile App Review and Submission Processes (2 hours) Overview of Emory's internal app distribution process Overview of Emory's public app distribution process Demonstrate completing an internal distribution request form Demonstrate processing an internal request to post an app to the Emory mobile app catalog Brief discussion of the public distribution request and process and how it differs from the internal process (more involved and time consuming) Questions & Answers 13-Jul-15 1

3. Agenda: Session 2 How Mobile Apps are Developed at Emory (1 hour 45 minutes) Types of mobile apps: native, mobile web, and hybrid apps Artifacts for the different types of mobile apps Criteria for determining which type to build Resources for mobile app analysis, budget planning, and development APIs and technical architectures for accessing Emory data securely from mobile apps Security and compliance implications of mobile apps Typical development and distribution lifecycle for mobile apps at Emory Questions & Answers 13-Jul-15 2

4. Examples of Emory Mobile Apps Internal Apps Administrative (HR Self Service) Research (Massive Transfusion Protocol) Clinical (Emory Healthcare Mobile for Clinicians) Educational (Post Transplant Meds) Public Apps (all born internally and first distributed internally) Educational (Surgical Anatomy of the Liver) Research (WebEase for Managing Epilepsy) Personal Health (ReliefLink Suicide Prevention) Our goal is to enable and accelerate mobile app development

5. Some Major Challenges 1)Funding 2)Development resources 3)Security, compliance & regulatory requirements 4)Distributing mobile apps internally during development, testing, and focus group/beta testing stages 5)Distributing completed mobile apps for review for internal and public distribution

6. Emory Mobile App Catalog

8. Emory Mobile App Review and Distribution Processes Emory defined two processes for review and distribution of apps: 1)Bound for public marketplaces 2)Bound for internal distribution Determined that an internal app catalog or app store was key enabling infrastructure for both processes

9. Emory Mobile App Review Process for Distribution in Public Marketplaces 1)Office of Technology Transfer Intellectual Property Analysis 2)Communications & Marketing Branding Review 3)Legal Counsel Review 4)Compliance & Regulatory Review 5)Information Security Review 6)Public Marketplace Submission There are many people involved in the internal review process, all of whom must review the app metadata, description, and demos and many of whom must study the app.

10. Emory Mobile App Review Process for Internal Distribution 1)Internal Posting Review 2)Compliance & Regulatory Review 3)Information Security Review 4)Internal App Catalog Posting There are fewer people involved in internal mobile app review, but infrastructure challenges are still formidable. Ideally, to enable and accelerate mobile app development an organization needs to: 1)Post apps quickly to a limited group of users working on the app 2)Expand that to developers and testers 3)Expand access to reviewers and approvers 4)Release to the production user base or entire enterprise

11. Summary Emory determined that internal mobile app distribution infrastructure was key enabling technology. 1)Key to enabling and accelerating internal mobile app development 1)Necessary to support a complex review and distribution process required by a large organization with many stakeholders

12. Summary Emory also expects it will be useful in other ways in the future: 3)Distributing vended mobile apps to Emory people 3)Curating lists of recommended apps in public marketplaces for Emory people

13. Mobile App Distribution Process Wiki Policies & Process Overview: https://wiki.service.emory.edu/x/8ILaB Internal Distribution Process: https://wiki.service.emory.edu/x/7ILaB

14. Posting Apps in the App Catalog Let’s demonstrate posting several different types of apps in the app catalog: Native iOS App (Emergency Codes) Native Android App (Emergency Codes) Hybridize an App (MTP)

15. Posting Apps in Public Marketplaces Major differences: Marketplace required metadata Marketplace required review/rework Demonstration and discussion

16. Major Types of Mobile Apps Three major types of mobile apps at Emory: Native Apps Mobile Web Apps Hybrid Apps

17. Native Apps Characteristics: Typically have richer user interfaces Run largely on the mobile device Store at least some data on the mobile device Interact with backend services at Emory via web services Can be designed to operate without wireless or wifi connectivity Have updates and need to be kept up- to-date Examples at Emory: WebEase for Epilepsy Surgical Anatomy of the Liver Emergency Codes

18. Mobile Web Apps Characteristics: Typically have simpler user interfaces Run entirely in an application server and web browser (not on the device OS) Accessed from a browser, bookmark, or browser-generated homescreen icon Typically store no data on the device Mobile device does not interact with backend services at Emory directly Require wifi or wireless connectivity to operate No updates that need to be pushed to the mobile device as it is a web app Examples at Emory: Massive Transfusion Protocol e-Vantage (EHC HR Self Service) Emory Healthcare Patient Portal

19. Hybrid Mobile Apps Characteristics: Typically have richer user interfaces Has a native mobile client component (usually lightweight) and invokes logic and presents content as a mobile web app May store data on the device Mobile device does may interact with backend services at Emory directly Typically requires wifi or wireless connectivity to operate Some, less frequent updates need to be pushed to the mobile device as it is a web app Examples at Emory: Massive Transfusion Protocol e-Vantage (EHC HR Self Service)

20. Criteria for Determining which to Build Does the app have features that must work offline? Frequency, volume, and complexity of data entry Device features: accelerometer, geolocation, peripheral device access Background operations Security Accessibility

21. Criteria for Determining which to Build Does the app have features that must work offline? Frequency, volume, and complexity of data entry Device features: accelerometer, geolocation, peripheral device access Background operations Security Accessibility

22. Resources for Mobile App Development IT Architecture and External Vendors: Help perform preliminary analysis Prepare a budget Develop Deploy Working with Purchasing to identity several preferred mobile app development vendors.

23. Look Under the Hood Developing iOS, Android, Mobile Web Apps High-level Architectures for Data Access High-level Security Architecture