O3 Skills Self-Assessment

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

This form will help us understand the before-and-after impact of your experience onboarding to OpenMRS 3.

Please be as HONEST as possible - your honesty helps us to learn where we can improve!

Email *

Rate your knowledge of the following O3 Frontend Technical Skills. *

1: This is new to me

2: I can find documentation on how to do this

3: I can do with a lot of guidance

4: I can do with some guidance

5: I can do with no guidance

I can describe the OpenMRS 3 framework to colleagues including apps, pages, slots, and widgets/extensions in O3

Run the OpenMRS 3 frontend locally & see local changes reflected in your browser

Configure your distribution with your branding (e.g. logo, brand colors)

Use configuration to set which apps and extensions you want, and in the order you want

Create a new frontend module using the openmrs-esm-template-app. This template app will help you understand how O3's model works, e.g. slots and extensions.

Use the Implementer Tools UI or JSON config to configure individual widgets, and practice by using the esm-generic-patient-widget

Reference the O3 Design Patterns for ideas and constraints

Go to the O3 online community to ask questions and share your work

Subscribe to O3 Release alerts from the OpenMRS community

Use the O3 form builder to create forms using mapped concepts

Config: Translation of HTML Forms to O3 JSON Form Schema

Extend the O3 form engine with custom expressions (e.g. validations)

Write API functions that communicate with your backend - call and grab data for a feature (e.g. from the OpenMRS FHIR API)

Create/expose an extension slot and render some piece of UI in that slot

Write tests: unit, E2E (in playwright), and integration

1: This is new to me

2: I can find documentation on how to do this

3: I can do with a lot of guidance

4: I can do with some guidance

5: I can do with no guidance

I can describe the OpenMRS 3 framework to colleagues including apps, pages, slots, and widgets/extensions in O3

Run the OpenMRS 3 frontend locally & see local changes reflected in your browser

Configure your distribution with your branding (e.g. logo, brand colors)

Use configuration to set which apps and extensions you want, and in the order you want

Create a new frontend module using the openmrs-esm-template-app. This template app will help you understand how O3's model works, e.g. slots and extensions.

Use the Implementer Tools UI or JSON config to configure individual widgets, and practice by using the esm-generic-patient-widget

Reference the O3 Design Patterns for ideas and constraints

Go to the O3 online community to ask questions and share your work

Subscribe to O3 Release alerts from the OpenMRS community

Use the O3 form builder to create forms using mapped concepts

Config: Translation of HTML Forms to O3 JSON Form Schema

Extend the O3 form engine with custom expressions (e.g. validations)

Write API functions that communicate with your backend - call and grab data for a feature (e.g. from the OpenMRS FHIR API)

Create/expose an extension slot and render some piece of UI in that slot

Write tests: unit, E2E (in playwright), and integration

Imagine you encounter a problem working on OpenMRS 3. Where would you go for help? *

OpenMRS Forum ("Talk")

The O3 Coffee Break Calls (daily dev support time every Monday-through-Thursday)

OpenMRS Squad Calls (eg O3 Squad, Feature Squad...)

O3 Slack Help Channel (#openmrs3-helpme)

O3 Feature Squads' dedicated Slack Channels (eg #appointments, #o3-performance, etc)

Other:

Required

Have you been onboarded to OpenMRS 3 already? (Meaning, have you already been through the O3 Dev Guide, and had some onboarding calls with other Devs very familiar with O3?) *

Not yet

A little onboarding - I have looked at some docs and experimented

Yes, I have been fully onboarded

Clear form

Never submit passwords through Google Forms.

This form was created inside of OpenMRS. Report Abuse

Forms