ACDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAIAJAKALAMANAOAPAQARASATAUAVAWAXAYAZBABBBCBDBEBFBGBHBIBJBKBLBMBNBOBPBQBRBSBTBUBVBWBXBYBZCACBCCCDCECFCGCHCICJCKCLCMCNCOCPCQCRCSCTCUCVCW
1
Calculated Field 1Skill
2
Collaborative ToolsCollabortive PracticesDatabase, data modelEmerging TechnologiesFrameworksModulesProgramming LanguagesQuality AssuranceStandards & ConventionsTools
3
StageDemonstrate the ability to manage builds Demonstrate the ability to use a version control systemDemonstrates the ability to manage projects using community tools (ie: Jira)Agility (Sprints, Spikes)Able to apply generally accepted OpenMRS data models, standards and processes in order to manage OpenMRS data and exchange OpenMRS data with other systemsMaintains current knowledge of market trends and the evolution of technologyAbility to use different frameworks based on the project or taskModulesAbility to decompose problems and systemsJava 11Maintains awareness of the different programming languages used by OpenMRSDebugging ProblemsOwnership of qualityAbility to communicate basic concepts of FHIR and their application to OpenMRSAbility to manage communication across systems using FHIRAbility to provide a working ETL solution for complex reporting problemsAbility to provide guidance to inform the design and infrasctructure of ETL technologies and solutions APISDKBash
4
5
/dev/1Explains what Maven is Review simple PRs submitted by other developers Claim simple ticketsComplete sprint tasks with directionExplain basic relational databases and ORM conceptsExplain when and where different frameworks are used based on the project or taskUses straight line code with copy paste for reuseIdentify the programming language used based on the purpose of the OpenMRS project, distribution, module, etcCan set up debugging environmentIdentify what could be automatedRecognizes SDK as an OpenMRS developer toolExplains what Bash is
6
/dev/2Uses basic Maven commands to compileReviews simple PRCreate tickets and curate simple ticketsCompletes sprint tasks with little to no directionWrite and explain more complicated queriesDescribe how to use a framework for a given OpenMRS projectCan write a Hello World moduleBreaks up problem into multiple functionsCan do basic debuggingAble to apply generally accepted OpenMRS data models, standards and processes in order to manage OpenMRS data and exchange OpenMRS data with other systemsExplain what ETL isNeeds to look up API documentation frequentlyUses basic SDK commands to ??DO WHAT??Knows basic Bash commands
7
/dev/3Can create a maven project with dependenciesMerge simple PRs submitted by other developers Create and curate complex ticketsLead sprints and to spike with directionAdds new classes and tables to the OpenMRS data modelComes up with reusable functions/objects that solve the overall problemQuery FHIR serverMake the data usable by loading it into a specified formatIdentify simple options for extracting data from OpenMRSHas the most frequently used APIs in memoryPerforms most SDK commandsKnows complex Bash commands
8
/dev/4Can deal with setting maven up in a complex projectMerge complex PRs submitted by other developers Can create epics and organize ticketsOrganizes sprints and spike with little to no directionResolves complicated ORM mapping issues (inheritance, etc.)Analyzes and evaluates data to determine or support decisions around, when to adopt new frameworks (i.e., lead, follow).Break up problem space and design solution within the same platform/technologySet up a proof of concept ETL solutionAssess ETL technologies that can be used by the communityWrites libraries that sit on top of the API to simplify frequently used tasksCan perform complex SDK commands
9
/dev/5Manage the project using MavenGit guru.Set up sprints and spikes that need to be doneReviews, recommends, and/or determines emerging technologies based on their valueCreates framework to develop an app or moduleVisualizes and designs complex systems with multiple product lines and integrations with multiple systemsProvide working ETL solutionsAdvise on the design and architecture of ETL solutionsCan contribute to SDK improvements
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100