Understanding functional and non-functional requirements is essential to successfully implement electronic medical record (EMR) systems. Actual requirements will be different for different contexts.To elicit and prioritize requirements for implementing EMRs in oncology in low and middle income countries (LMICs), and to relate these to requirements from high-income countries.Cancer care stakeholders including oncologists, general doctors, nurses, biostatisticians, information technologists, from different LMICs, were involved.Concept mapping was used. Statements of requirements were obtained during focus group discussions (FGDs) and interviews. Using surveys, the requirements were clustered and ranked on importance and feasibility. Data were analyzed in SPSS using agglomerative hierarchical clustering and multidimensional scaling, to create cluster maps and go-zone maps reflecting the relationships between the requirements and their prioritization.Four FGD sessions, with twenty participants, were conducted. In addition, six participants were interviewed. Twenty-two participants clustered the requirements and sixty-three participants ranked them on importance and feasibility. One hundred and sixty requirement statements were generated which were reduced to sixty-four after de-duplication and merging. Nine clusters were obtained encompassing the following domains, in order of importance: Security, Conducive organization, Management/Governance, General EMR functionalities, Computer infrastructure, Data management, Usability, Oncology decision support, and Ancillary requirements. On ranking, the requirements scored between 3.74 and 4.80 on importance, and between 3.55 and 4.46 on feasibility, on a 5-point Likert scale. We generated concept maps for use when communicating with stakeholders.For oncology EMRs in LMICs, requirements overlap those from high-income countries, but generic EMR functionalities, Infrastructural and organizational requirements are still considered priority in LMICs compared to oncology-specific requirements or advanced EMR features e.g. computerized decision support or interoperability. Concept mapping is a fast and cost-effective method for eliciting and prioritizing EMR requirements in a user-centered manner.