 Thanks everyone for being here and it's always nice to meet everyone here online and it's an honor for us in HEPS Indonesia to present to you the what we have developing about Jumpa Doctor and here I am with my colleague Ari and yeah okay so the point in this presentation he is we are trying to develop EMR like basic EMR that's why we call it simplified EMR by using the H2 engine yeah thanks so basically in this presentation we will present about what is Jumpa Doctor and what are the ecosystems involved and to be more detailed in the mobile in the doctor platform and also as the DH2 to Satu Sehat the Satu Sehat is actually the data exchange platform newly imposed by a minister of health of Indonesia which use a fire and also medical standards that should be used in any healthcare facilities in Indonesia so there will be a mass for all the healthcare facility to connect to the data exchange platform called Satu Sehat so let's move to the next slide okay so Jumpa Doctor it's Indonesian term actually we can call Meet Doctor or Meet your Precision so since this Jumpa Doctor is not only one application it's a we call it ecosystem because it's involved in various application and it's basically a medical electronic medical record that handle the management that handle the health service we serve diagnosis and medicines the coefficient of the Jumpa Doctor is the we want to help any private health facilities because it's sometimes it's it it's not affordable to subscribe EMR which offered by many vendors here in Indonesia so that's why our vision it's we want to help the private health facility to use or implement electronic medical record and at the same time as I mentioned before the MYH Indonesia impose all the healthcare facility to use electronic medical records by 2023 and here for the summary the Jumpa Doctor we use the HS2 engine as a cord so it will be in the middle to conduct everything it's a brain previous light first massage previous one yeah and also the Jumpa Doctor also will have facilities to manage health service we serve and also the patient medical record and now Jumpa Doctor it's currently under development with the integration that I mentioned before we use fire for to support to support the Indonesian health government damage interoperability for health information and the and also as as an additional information we use several you know technology to create a web and mobile like we use node gs react and flatten next okay so this is why we call Jumpa Doctor it's not a single app but this ecosystem by using the HS2 as a core element on this so there is Jumpa Doctor web app we use we use it for managing the schedule the service schedule and also for the medical record entry and also we also have Jumpa Doctor mobile that manage for the appointment or the booking service for her facility and by that we use also a middle work the api bridge to bridge between Doctor web app and also Jumpa Doctor mobile and also we use the api for standard ice terminology such as ICD 10 and ICD 9 maybe Mas Ari can all can elaborate more on the technical side of things but I will continue to Jumpa Doctor admin here we can manage the service schedule we can also the manage price because in healthcare facility they also need to even even it's a small practice it's a private clinics for example it also needs needs to be in electronic medical records so that's why Jumpa Doctor wants to help them to implement this kind of service and and last one we also in the development of DH2 to Satose Health platform which act as a data mapper and interoperability layer for Jumpa Doctor to Satose Health which I mentioned before as Indonesian health data exchange protocol next yeah this is the example of Jumpa Doctor mobile it's it's basically a flutter and fire based mobile based application and this is integrate with the Jumpa Doctor DH2 engine over api bridge and of course the race api and Jumpa Doctor mobile it's actually uh it says we call why we call simply fight EMR because in this user friendly mobile app people or patients can access and order their healthcare service even they can do the virtual consultation whenever and whatever they want and for the authentication Jumpa Doctor use OTP authentication by using point number that actually makes Jumpa Doctor easier to use next and for the doctor app we built this by using react and not yes that integrate this too and bridge and race api and also this application provides several features like we can view list of patients here list of patient medical records and also even the schedule for health service so I would like to highlight here because maybe maybe some if some medical background persona will see this oh why this is so uh so uh short although why this is so simple because uh this Jumpa Doctor it's it's uh we focus on the private uh doctor so uh every for example the doctor want to uh conduct the practice we have done with these uh tools because uh uh as I mentioned before it's imposed already by the government to use any uh to use electronic medical record for any kind of healthcare uh facilities including the private clinics or private um uh GP for example next so uh this is the uh the one that my my colleague Ari will uh elaborate more but basically uh this is the green one is Satu Sehat logo so all the healthcare facilities in Indonesia should connect to Satu Sehat and Satu Sehat use uh fire as a standard for uh exchanging the data and also use ICD-9, ICD-10, SNOMED CT and LOIN for the uh medical terminology so um in terms of um transforming the data from our DHS2 to Satu Sehat I will let uh my colleague Ari to explain more about that go ahead Ari I'll stop here can you hear me clearly there yeah your uh so uh let me continue the presentation thanks Masaldi for the presentation first so uh what is this DHS2 to Satu Sehat platform is this is one of uh the part of the Jumba doctor ecosystem that we built for uh data integration or data uh data exchange between Jumba doctor or DHS2 uh with the Satu Sehat platform that they used to FIR data standard for exchange data but uh how the data flow from uh this duo to Satu Sehat or fire so uh from the DHS2 uh we have built one uh custom application that could be installed in the DHS2 uh platform that will provide some uh some data exchange sample or template so for uh data exchange from this duo we take you from track entity instance organization units and events for uh data exchange to Satu Sehat so uh before uh data exchange uh process uh will do we should create some uh data template or data exchange template that uh will convert data adjacent from the DHS2 to more simplify adjacent simplifying that could be map or could be transform or convert to uh fire or Satu Sehat uh data adjacent structure next uh this is the flow uh for Datamipeng Datamipeng flow from the DHS uh to adjacent structure or like track entity instance organization units and events will convert to adjacent simplify provided by uh DHS2 to fire back end to Satu Sehat back end and then from the adjacent simplify uh the DHS2 back end uh to fire back end will convert the adjacent simplify to fire or Satu Sehat adjacent structure so uh this is some uh UI in the DHS2 data to Satu Sehat platform so basically there are uh some features for features in this custom application we helped build but this is under uh still under development uh the first feature is dust board that to view uh how much data that successfully uh sent to Satu Sehat and how much data that failed to send to Satu Sehat and then uh there are a feature named template here so uh the template will provide how we create the Datamipeng scheme or Datamipeng template that will use to map the DHS2 data to adjacent simplify that will use uh by DHS2 back end uh to send the data to Satu Sehat platform so this is the uh how we use the template scam that we created before in the feature template features so for the poor data sending mechanisms we use Q mechanism in here so from uh from uh template scam that we created before the DHS2 fire platform or application will automatically map the DHS2 adjacent structure to adjacent simplify uh scam template like here before so and then one uh the last feature is settings here uh this is just the configuration for the DHS2 application to fire application there are uh configuration for uh DHS2 to fire back end URL and the Satu Sehat fire URL or fire URL the client ID and the client secret to connect with the Satu Sehat platform so uh this uh overall for the presentation but let me uh demo some uh process in Jumpa doctor ecosystem for uh from how patient uh book booking the the service and until the this dual DHS2 to fire to Satu Sehat we'll process the data uh let me share some screen first for the mobile application uh Ren sorry can I uh I am doing with another another account here can I uh present yeah um you have another account already in or yep I'm sorry what is the name I see him yeah okay all right you should be able to present there as well and thank you Zaldi for answering question in chat so maybe take a while yes I can see your your mobile now yep uh for the mobile application this is this is how the application the Jumpa doctor mobile application look like first maybe we need to login to the to the application we use phone number for application here need to put some on time tp here okay and this is the first page in this Jumpa doctor mobile look like there are some features here for for the first section is uh the uh the type of the health service in here like a general service or COVID-19 test and some uh health service uh another health service for the test here for the demo I will try to create some service here for myself uh I need to put my uh my condition for the health service here like just symbol maybe sick and then next we choose uh one or two type for the service there are health uh home care service or we uh the service we want to visit the health facilities we try to choose the health facilities service so we need to after this booking created booking service created we need to come to health service to receive the health services we choose the facilities let's say this one and choose the clinics and then we choose the doctors and next you know we choose the schedules from the date we choose this day and the the hour for the service the time sorry the time we choose the 9 o'clock 9 p.m. o'clock next so this is okay we have successful successfully created the health booking service so after this process was finished uh the first-gen booking service data will show in the let me present one one page again it's called for uh the jumba doctor the the doctor web uh the doctor web platform so this is the sorry let me use another another chrome profile so uh okay okay i will continue so after uh patients book a service from jumba doctor mobile the service will ever hear in the the website here with the so the q entry in the website a doctor after uh to receive uh to serve the first-gen for health service uh doctor just click this service one of the service and add some uh click the bottom for at the health service data or uh electronic medical record data the first section is for uh physical assessment for the patients like the general condition and the uh vision uh the the human vision systems and uh etc here there's a lot of data entry here for uh patient medical record and also uh the diagnosis section the the diagnosis uh uh data we use uh icd10 standard like uh we just put some uh uh diagnosis code and that provided by icd10 standard we just just one of them and then add some notes like uh uh condition notes here one of the others thing and just the add button and save the diagnosis it's yeah so uh after this process uh uh uh finished doctor health uh has has entered the patient medical record by health service we can uh continue to send the patient data for the medical record to satuahat with this dua to satuahat web application uh we can use another here oh sorry i need to install some let me go to the this platform first okay uh first maybe we need to install the uh this dua to satuahat the web application first in this this dua application and we will uninstall the the last one i i have installed first has been installed let's open this application yep uh this is the this is the h is to satuahat web application that was installed to this dua so the first step to uh send the the patient data or medical record data that was created before by doctors we could template first to create the mapping data that i was uh introduced in the in the slide on the presentation first we need to add some title for the data mapping scheme or template like then we need to select the uh this dua research for the for this time we just provide to uh add to this dua research time organization and event because in this development process we still need to elaborate our metadata and that support the satuahat data requirement so let's test this let's test this with event so we need to select the program from this dua uh for we select the patient registration and select the program state for uh health service booking and then we can select the the target result to satuahat result but in this result we'll provide the jason simply by structure that provide by the h is to to satuahat back end for the uh pacien booking service data in the satuahat the result we use and counter result after we have select uh that record and fill uh in the section below we'll show the requirement uh they required the jason simply by structure that we need to map so for the practitioner and iqa there so we need to provide the uh the field for uh doctors identifier that we that this is to uh to satuahat need to get the doctors data so let's just fill the form for uh for any kind we use id doctors they're taken from uh data elements for the from the data fields of events and then created that from the even created and then for the satuahat result for pacien and iqa we use an iqa reference and then the h is to oh we widely we use what you need from the event and then the last one is the event id we use the event id after that just quit the just set the mapping and then we move to the q and let's quit the new q here we need to select the template scan before uh we have created before let's select this one and the system automatically will sew the uh data method from the h is to to this and simply buy so to uh uh to add this uh data to send uh by the h is to so to satuahat back and we just need to select or check the checkbox in the website uh so the system will save this data uh to send by q system after we uh check data just save the q and then we move to the q feature and then the data before that was selected on the create q will add for here so to show the details from how the structure was changed just click the so detail here so we can view the uh different of jason simply buy that was converted to uh to satuahat or fire jason structure here so uh that is the whole of process of yumba doctor ecosystem until uh from passion booking the health service until the h is to uh send the passion data to satuahat or fire affect form so the next is uh should i uh sew the the sum of the codes of the programs rain um yeah i don't know if there's any questions that are unanswered because sully is very active in chat and so thank you for that um that does save a little bit of time there i'm not sure if there's any anyone has any questions feel free to put them in a chat and get them answered there um i i'd say go ahead to the uh to the code yeah i think uh some people might be interested in that if you have yeah okay let's me continue to the core right maybe for the first i will uh yeah i will present the uh jumba local mobile first sorry for all of the here where he's so this is the the jumba doctor mobile code that built by flutter uh there are some uh yeah we we know how the flutter the flutter structure for the program maybe for the i will uh tell about uh where is the uh the state management for the state management from the flutter we use he the bloc oh wait i think we use providers here um maybe rain can you recommend me how to hide how i must uh describe the coding because i don't know how i begin it but but it looks a bit it's it looks very uh complex application already um so um that's a good question um i'm guessing a lot of people here are interested in in like how you um and also based on the questions we've saw is it's like the the fire integration itself but that's not the mobile application if i understand that correctly um but also um how you manage the data in general i think that's a good one to look into i mean there's no time to to show the entire application um so how do you integrate with dhs2 how do you integrate dhs2 with fire those two topics i think are most interesting to look at okay okay uh how we integrate the the the doctor application and the jumpa doctor mobile uh application with dhs2 dhs2 uh web so uh from the jumpa doctor mobile application will connect to api bridge by uh restful api and then let me show the presentation layer sorry the repository maybe where is that one this is the yeah uh the the codes look like for the this api integration for from the jumpa doctor mobile with flunter to api bridge before so basically the api bridge just uh just the the middleware uh between the between the dhs2 with jumpa doctor mobile and just uh jumpa doctor mobile just request the data by uh the api uh the api that follow the dhs2 api so uh just just the the the simple simple way we we integrate with this so uh in jumpa doctor mobile just for fatwa for middleware uh jumpa doctor mobile authentication just use firebase with a one-time password for authentication and uh after that the jumpa doctor mobile can connect it with the dhs2 and then um maybe i will move forward to another uh api bridge begin um i just wanted to add to to those that didn't see the message in chat like if anyone here has any specific requests to see in the code now is the time to ask of course um there's only so much i can think of um and uh if you're interested in anything from the code i just speak up in chat and we'll get to that thank you uh let's me continue the presentation right so for the uh maybe we continue to the api bridge back okay here another yeah this is the i think the the code is more uh very very complex because a lot of program or a lot of application that connect with the dhs2 so in this dhs2 api bridge we create with node gs and with express gs to perform the recipe i service that also this this application integrate with firebase administration that will use to validate the authentication from jumpa doctor mobile in this uh in this uh application node i specification we add some uh third party service like icd 10 api to add the icd 10 standard for the uh the apnosis code and the icd and the medical record number generators also for the fgm for notification to uh jumpa doctor mobile but if uh you guys want to view the code maybe uh after this i will host or upload this uh the code whole of jumpa doctor code to our github for public after we remove some uh some secret file in here so we can upload that that's great okay for the data right okay so for the maintenance maintenance where is that um actually we don't use open in this jumpa doctor ecosystem can you tell me what what you want to show in the maintenance menu maybe about our metadata okay programming in the case here okay for the metadata in here we have quite several programs the first program is for post-gen registration for a hot surface and the second program is for uh physical assessment the third program is for the apnosis and the the port program is for hot standard operational for serve the patient and then for the rating for the program for the doctor and this one is the new new program we have created for enhancements to say hot connection this is just for uh organization look organization details like uh follow the the organization phone number and the organization location and and then the one we have great is uh event program for save the uh jumpa doctor mobile application rating and then for the tracking entity entity type we just used to uh track identity type here for people and the last one for uh allocation uh details and then for the maybe about the for track identity attributes there are a lot of attributes we have created here like uh uh patient religion uh address and the pacien identifier like an ic or passport and then uh a doctor uh address and uh basically for the doctor profile data and patient profile data and then for data element maybe uh also we use the element here to save the electronic medical record data like the physical assessment result for the human vision and uh and etc there are a lot of the the elements here and then uh organization unit maybe basically this is this server this is the server is our development server so maybe there are a lot of dummy data in here um for the offline mode we we still don't try to develop for offline mode but maybe in the future we can provide because fully uh this system connected online uh some of features can be online like uh uh in jupy docker mobile we provide the location for pacien location for maybe a pacien booking for home care service so the doctor can uh know the pacien location for it can you please answer claude mamo from ui all questions about uh running the dh2 fire routinely or do we need to trigger it manually um because we after we create the mapping or the queue uh maybe not routinely but the trigger was created uh after we create the queue by related to the damage game so not not true i yeah it's it's a lot right um and i like i have a i have a question is um you you mentioned you were gonna open source some of your processors does that include the the flutter application and the the app as well uh that you're that you're displayed the the synchronization app between fire and dh2s will you open source those uh currently for the uh for the data integration uh still on development or still in mocking uh modding because we uh still on enhancement for metadata to support the to clearly complete the requirement data to hi all right yeah um but yeah of course if you do when you do open source it would be great if you post it on the community and let everyone know that that it's there i got a question from berwick who sent me a message directly um is that how do you connect and set up a fire server to connect to dh2s too like is there any logic in your code that um you can show or is that too complex to uh to show yeah but yeah uh for the credentials stored maybe uh where we save the statistical credentials uh basically we store to the dh2 uh back end to satoose hard database database that we use custom database in in there that we store uh the result of uh data reference but the that is not implemented yet so what we have so in here just uh our progress uh until now so that's very uh much to add a very lot of things to end helpful so so important all right so we only have a few minutes left um what what i recommend doing and and i feel like there's a lot of questions that are unanswered or people have that they even haven't typed yet um they're this this this meetup is recorded um so i will publish this and then put it on the community portal on the community of practice um and uh with the video attached to it and maybe we can continue the conversation there so if ari and sully are also okay with that then we can do a conversation over there um there's still some some time left now to answer one or two questions um but i feel there is like if you if you looked at the code it's it's very complex and we've only looked in a couple repositories so i can imagine it's uh it's a little much to take in um so and also we can probably share the slides on the community on the c o p as well so that would be good um then there is a a little thing you can claim i put it in chat right now you can click the link that i posted in chat if you want to have a badge on the your community of practice profile um and then you get a nice little badge you can show off on your profile that you've attended the developer meetup so in case you're interested in that that would be great and if you already have one you can collect a second or a third or a fourth like you can see it as a achievement for yourself and uh and yeah so click it and accept and then you will be granted after the meetup um but yeah if there's any further questions that we can look into or Ari or Sally if you have anything um to say that that can wrap this up that would also be good like what what more information are you holding back yep for me maybe that's uh all that i can uh i can uh thank you thank you maybe that's all i can tell you guys uh sorry not tell but that what i can uh to uh to share for our progress in this application maybe until this our development was finished and we have we have the code clean more clean and the the system was working well we can publish in uh the GitHub or uh the this do a application uh application help that's it maybe Masaldi can is there anything else yeah all right uh i just want to say thank you for the uh the GOP committee as well and also all the participants coming here it's it's it's nice to share to everyone and also we get so much questions and input that we really really consider for the next improvement of our app so it's it's really meaningful for for us and also i kudos to Indonesia team here we have Ratty we have Yuda we have Zulkipi thanks for the um good work so far and hope to get more impact to the community and also get more learn from the community thank you