micado-eu / micado Goto Github PK

• provide information as faq or articles
• connected to B3 (Info on Housing Market)
• example contracts translated to different languages
• killer feature also outside of MICADO

• is this about internal feedback on how to use the app, or on the actual UX? Hakan: How is MICADO working, how successful is it
• Or analytics about user experience regarding the graphic design etc?
• Two parts: analytics / design
• GENERAL REMARK: UX needs to be thought about regarding the mock-up / prototype now as a second step, at the moment it is not sexy 
• there are analytics tools, but who is doing the analytics – the authorities? In HH, the authority for work (BASFI) is interested in this data

• two options: 
    ◦ (1) purely informative, FAQ style with links = easy; 
    ◦ (2) decision tree system, dependent on that the user receives results → more complicated to implement
• additional: links to unions possible to apply 

• there are existing services, but not standardized
• combination of information/availability? Or a dashboard for NGOs where they can look up a specific translator
• points lowered from 6 to 3

• minimum product: links / FAQs / checklists for what is helpful when applying for a flat or for how to obtain a “Wohnberechtigungsschein”; on additional information like waste collection etc
• additionally (and added value): comparison table to find out how expensive different forms of housing are over time (cooperatives, social housing, regular flat) 
• changed points from 6 to 5

• tool to facilitating different actors to cooperate
    ◦ example: passing information like a relevant social worker’s name between two PAs
• part of technical solution: “it’s me” for identification → with that tool it becomes powerful for migrants
• what is the minimal info that has to be shared? 
• it’s for sharing of information about a migrant between two PAs when that migrant has consented to this sharing; also possible for migrant to share data with PAs

• Antwerp has a high competitor for this function, but the data is open so we could use it
• categorisation issue also
• one of the most critical needs/demands (education key to getting to job market)
• there already are institutions that do that
    ◦ but they are multiple (e.g. in Germany profession-dependent), so guidance / general information could be useful
    ◦ Atlas also already provides information on the process on their website and a specific team to council 
• > overall points raised from 6 to 8

• it’ll be very hard to implement, because it depends heavily on country of origin
• data availability scattered, difficult to aggregate all information for all cities
• availability low, but criticality really high; it could mean the difference between staying in the country or not
• in legal/delicate issues it’s difficult for MICADO to offer advise
• Luca: let’s remove the word ‘advise’; either we describe processes or we don’t
• MICADO can inform about processes, but not advise; rather map and describe processes, even if MICADO isn’t owner of the process
• GENERAL REMARK: actors need to be defined who regularly update information on process →  needs to come from the LESC, if we have decided on specific functions/processes we want to describe within the MICADO we can present it at the next LESC meeting

• similar to B4 (simplified version of it)
• general information on process in domain of health
• medium criticality, good technical feasibility 
• GENERAL REMARK: important legal concerns: we must not advise, only inform
• could be a feature of the doctor finder map?

• there are other time management tools
• question: could it be possible to integrate MICADO with the phone’s calendar?
    ◦ it’s probably not more than a nice-to-have

• Lagebild could be a starting point; Antwerp has a similar collection of data sets (needs to be checked how much they align)
• responsibility for updates with the data owner 
• Luca: could we have some sample data (a .csv file)? I would be eager to use this to start developing an evolving prototype

• Data availability: high; Atlas has structured info on processes
• process knowledge: need understanding of categorization of users: nationality, gender
• translate it into a graph/chart
• more or less a tutorial of how to apply for health insurance/gather information; but will be not very attractive for authorities
• > no operational issues/competitors obvious
• > John: would the process of applying be supported by MICADO?
    ◦ Answer: in the group conversation, we haven’t talked about it; in Antwerp an informal comparison between services would be interesting > for MICADO we provide information; but for MICADA we have to keep in mind what else we want/need to develop
    ◦ Luca: let’s not do it
    ◦ Minimum solution: collection of links, additionally tutorial possible
    ◦ Luca: idea: instead of recommending health insurances, maybe we could do a rating system (rating by end users, not by PAs) 
• so this single service wouldn’t be unique, it would be doubling what’s available elsewhere (but the combination would be making MICADO unique)
• simple sheets for quick comparison

• there are better contestants on the market already for messenger services, not in the scope of MICADO (FB messager, whatsapp) 

• compared to  obvious services like Google, MICADO’s added value would be e.g. language of doctors, combination of information on hospitals and 
• combination of general information & procedures 
• services on health, education, employment, culture, … should be located in a map
• GENERAL REMARK:  the more information we have, the more updating needs to be done
• Luca: we need to be sure we (will) have data before we develop a feature
• many concerns and intricacies about being allowed to use data
• we need to clarify if we can get the data. Homework for Hamburg: ask Triaphon about their list on doctors’ speaking languages and whether we can use & publish it (as for the other domains)
• here, filtering feature will give added value (by gender, language, free / not free) 

• for common understanding and translation, but more: a repository of definitions
• ambition: could we make the glossary trustworthy and reliable on the information provider
• possible downside: there may be a necessity for a lot of different actors to update / feed this
• more useful for public organizations that are not so much specialized, but not so much for migrants? For them, more a description/sample of documents would be important to them
• users read text on app and can click on some of them to get explanations on the terms
• added value: visual/audio glossary to make it more accessible

• explanation on free treatment and who is eligible for it 
• information comes from health insurances 
• out of MICADO’s reach to provide holistic information on health care services, but links can be provided to insurance service numbers + instructins how to best approach them (have your insurance numbe ready)
• links & FAQs on these issues is most feasible

• = filter info based on legal status
• availability: data available upon logging in in the app (= not topic-by-topic)
• feasible, but high research / development effort, and the tagging/filtering will most likely be not very specific
• reminder to update status 
• the functionality would be there in order to help user filter stuff they don’t need, but it will probably not be really used because people will tag everything “visible for all”, so it won’t be of use to put effort
• maybe having this feature would be a good selling point
• long discussion in the group, part of the group would increase

• digital databank but not the same as migrant monitor
• there is an overlap between C2 and C4; 
    ◦ C2 more a business intelligence tool / statistical; 
    ◦ C4  activity oriented  
• data update is a problem. Pas / NGOs might be more interested in using this when actually migrants are using the tool
• this is a data table that needs to be filled in MICADO
    ◦ could/should be started utilising the LESCs