@mr.paul download CDM for a few hospitals. You will notice there is a lot of difference in each hospital’s CDM.
We need to parse each CDM with proper column names and store it to github.
Example
One Hospital has column name for “Price” as “Charge” while other has “Unit Price” We need to make all columns with proper name and save it to github.
Then only we can access CDM properly.
Yes I know that
then I guess you suggest to use GitHub as a database?
Exactly, We can use Github as Database because it is free to use.
If use Github as a database, where will you do the processings? LH servers? 
Yes, for first time we can push data manually, then later we can use LH servers to update
Or… we can write a script for first time, as well as it will run periodically every few hours on the LH servers to update the database (in our case GitHub).
Yes, we can do that also
Hi @shuvo, welcome to LH. Please read the project’s description and this thread for relevant tips on how to get started. If you have any questions feel free to reach out
But why are we using GitHub again? Will we ever use the version control system? Won’t we always fetch the up to date CDM data.
We aren’t storing anything in our app, right? Then there’s no point of using GitHub? Let’s use Firebase to say, we can atleast query for particular hospitals and procedures there?
Should we use Firebase Database or Github to store CDM.
But, we may need to purchase in future if we use firebase database
@sunbiz wanted us to use Git for maintaining changeset so that we don’t have to manually update the database. But I guess using our own backend and updating the database suits our purpose. And opening endpoint for fetching specific hospital and procedure details.
I don’t see the need to use ETags, or git or firebase to say. We will fetch CDM details only when the users request and only for the hospitals that’s nearby to the user.
And also we are supposed to be developing RESTFUL backend (as stated in the project), which will further be useful for connecting other clients.
This Organisation will have to bear the cost if we use other backend server or database. That’s why they have asked to use Github.
Yes I fully agree with that, and that’s the reason I am against using any kind of 3rd party service. If all we are doing is using GitHub for database, then why not use MySQL integrated with our backend which will be running on LH server?
It will create pressure on LH server everytime user searches for anything. So, LH server will be used to only update the database(Github) once a day or week.
I get it. So the main computation will happen on user’s device. Like for 10 nearby hospital’s the user will fetch CDM for all 10 hospitals, then look for the particular procedure. Then the entire project comes down to an android app.
Then that day @r0bby was trying to say the same thing. We fought for no reason 
Yes, after downloading Nearby Hospital’s CDM app can also work offline
But, that day @r0bby was saying to do webscrapping also in app. Now @sunbiz gave us idea to use github as database.
we combined both ideas
Yeah, now we got an intermediate - GitHub. Now it’s clear and concise.
@sunbiz @judywawira @muarachmann @r0bby Please check on my draft proposal, I have completed the prerequisite task. I have used REST API back-end to return hardcoded response for now.
I am planning to improve on suggestions provided by @sunbiz in the above discussion.
I think it would be an intensive task and memory wastage if we planned to store cdm of all hospitals in the Mobile App itself.
I would suggest to view all hospitals when queried for any procedure. If the user find some hospital preferable, he would mark it favourite and its data will be store in local database for offline viewing which would be in sync with the Firebase Database.
A back end server would be required to update Firebase database on a periodic basis this is because all cdms do not have a proper format. So, it would scrape and standardise the format and store it in Firebase Database.
@sunbiz @r0bby @muarachmann Will it work?
@tazril Suppose a user has 10 nearby hospitals, Then 10 hospital’s CDM will not require more than 10 MB space. It can be stored in app