search

jupyterhealth / jupyter-health-software

A repository to track issues for the JupyterHealth Software Team
0 stars 0 forks source link

FHIR Service Deployment #2

Closed colliand closed 3 months ago

colliand commented 3 months ago

This is a stub issue extracted from a brief comment in the running notes Google doc.

FHIR Service Deployment: The need to set up a FHIR service capable of aggregating data from wearable devices.

colliand commented 3 months ago

This issue was created based on discussions in the December meeting. I believe TCP has decided to use a different approach that will not rely upon the FHIR service from AWS. If that's actually the case, I invite @surfdoc to close this issue.

surfdoc commented 3 months ago

That is correct. Instead of trying to stuff the OMH data into a text field in the FHIR Observation resource (which was the plan to complete the March 30th initial pre-mvp deadline) we are going to store the data in OMH format in a Cloud Storage Service. We are shimming the data for the pre-mvp from iHealth format to OMH format within the CommonHealth application on the user's Android device. Post MVP we may look to shim the data to FHIR format and storing in a FHIR Cloud Storage service but that is out-of-scope for the MVP.

surfdoc commented 3 months ago

@maryamv - I don't believe I have permissions to close issues. Could you elevate my permissions? Thanks.

maryamv commented 3 months ago

@surfdoc, done! -- You should have the necessary permissions now.