1. To ensure the access and use of digital health innovations for patients and citizens (e.g., libraries / repositories).
2. To provide policity makers and funders / ensurers with necessary information (certification processes for reimbursement).
3. To inform and assist healthcare professionals.
4. To provide good practice guidelines for developers (general guidelines).

1. How are health apps legally defined in the country.
2. Level of app complexity included.
3. Languague and other country specific facts.
4. What type of evidence related to the apps is needed? (e.g., voluntary or reimbursed).

1. To involve experts and organisations to ensure all aspects can be addressed and evaluated and updated.

1. Certain criteria apply to all frameworks use-cases (e.g., security and privacy). Others depend on the classification of the app type and requirements.

1. Consider workflows such as: self-assessment by developers; expert assessment.
2. Specific phases of assessment can be defined.

1. New regulations and standards.
2. Refinements based on experience and lessons learned.

1. Evaluation of cost, incl. platform maintenance.
2. Partnerships.
3. Sustainability pathways and business models depends on the purpose of the evaluation: public funding; perceived fees for assessment / apps in the repository / reimbursed apps; yearly fees.

Technical implementation of the library.

To detail information on the website about:

1. Language and scope.
2. Transparency.
3. How the repository is updated / maintained.
4. Helpful information about apps for end-users.
5. Search filters.
6. Clear process for delisting or archiving apps.

1. To identify other end-users of the AF to spread awareness.
2. Communication and dissemination.
3. Training with healthcare organisations and professionals.

1. To encourage reflexive learning, what worked, what didn´t, and adapting the process according to the lessons learned.