Add location mapping widget #800

f-odhiambo · 2021-09-28T13:53:53Z

Is your feature request related to a problem? Please describe.
Add a location widget that allows you to submit the location with GPS coordinates and location details as FHIR Location resources
Describe the solution you'd like

ANC Usecase
In the ANC use case, add a location of a facility or a family residence or village during a family registration/enrollment Encounter that will in turn reference a Patient plus a Practioner. Tagged via Encounter.location This should submit a location payload tagged to a patient while enrolling ANC Clients or registering a family and its householder members
Covax Usecase
In the Covax demo app, allow a user to submit the location details of where the Vaccination is being done

The Widget should be able to trigger the GPS to collect Latitude and Longitude coordinates for a precise location

Sample location payload for an Immunization facility

{
  "resourceType": "Location",
  "status": "active",
  "name": "Arundel mobile clinic",
  "description": "Vaccination Site",
  "mode": "instance",
  "address": {
    "city": "Nairobi",
    "state": "MD",
    "country": "USA"
  },
  "physicalType": {
    "coding": [ {
      "system": "http://terminology.hl7.org/CodeSystem/location-physical-type",
      "code": "bu",
      "display": "Vaccination Center"
    } ]
  },
  "position": {
    "longitude": 42.256500,
    "latitude": -83.694710
  }
}

Describe alternatives you've considered
N/A

Additional context
Sample location payload for an Immunization facility

{
  "resourceType": "Location",
  "status": "active",
  "name": "Arundel mobile clinic",
  "description": "Vaccination Site",
  "mode": "instance",
  "address": {
    "city": "Nairobi",
    "state": "MD",
    "country": "USA"
  },
  "physicalType": {
    "coding": [ {
      "system": "http://terminology.hl7.org/CodeSystem/location-physical-type",
      "code": "bu",
      "display": "Vaccination Center"
    } ]
  },
  "position": {
    "longitude": 42.256500,
    "latitude": -83.694710
  }
}

Sample location payload for a Household location/home

{
  "resourceType": "Location",
  "status": "active",
  "name": "Kasera Village",
  "description": "The home village location",
  "mode": "instance",
  "address": {
    "city": "Nairobi",
    "state": "Kenya",
    "country": "Kenya"
  },
  "physicalType": {
    "coding": [ {
      "system": "http://terminology.hl7.org/CodeSystem/location-physical-type",
      "code": "bu",
      "display": "Kasera Village"
    } ]
  },
  "position": {
    "longitude": 42.256500,
    "latitude": -83.694710
  }
}

Sample ANC mock

NB. The accompanying details of the Location (address, display name) can be collected via a questionnaire and appended to the Questionnaire response before extraction and saving/posting/sync as a location resource

The text was updated successfully, but these errors were encountered:

jingtang10 · 2021-09-29T08:11:01Z

What would the questionnaire response look like? It should be a response item to a single questionnaire item?

f-odhiambo · 2021-10-08T07:58:59Z

@jingtang10 There is an R5 ballot on the use of geolocation https://build.fhir.org/extension-geolocation.html. Added a zullip chat on this https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Location.20mapping.20widget Will keep reviewing and try and draft a suitable QuestionnaireResponse

f-odhiambo · 2021-10-12T08:52:51Z

There is an R4 extension for GeoLocation http://hl7.org/fhir/extension-geolocation.html. Which could be used to append the location details directly to the Patient Resource or just used separately as in a Questionnaire to get location details. I think the QR can take the following form

{
  "resourceType": "QuestionnaireResponse",
  "status": "completed",
  "subject": {
    "reference": "Patient/969",
    "display": "Test Patient"
  },
  "authored": "2013-06-18T00:00:00+01:00",
  "author": {
    "reference": "Practitioner/970"
  },
  "source": {
    "reference": "Practitioner/970"
  },
  "item": [
    {
      "linkId": "1",
      "text": "General questions",
      "item": [
        {
          "linkId": "1.1",
          "text": "What is your Country of birth?",
          "answer": [
            {
              "valueString": "The Netherlands"
            }
          ]
        },
        {
          "linkId": "1.2",
          "text": "What is your City or State of birth?",
          "answer": [
            {
              "valueString": "Amsterdam"
            }
          ]
        },
        {
          "linkId": "1.3",
          "text": "What is your Village of birth?",
          "answer": [
            {
              "valueString": "Kraule"
            }
          ]
        }
      ]
    },
    {
      "linkId": "2",
      "text": "Location Details",
      "item": [
        {
          "linkId": "2.1",
          "text": "Latitude",
          "answer": [
            {
              "valueString": "52.3676"
            }
          ]
        },
        {
          "linkId": "2.2",
          "text": "Longitude",
          "answer": [
            {
              "valueString": "4.9041"
            }
          ]
        }
      ]
    }
  ]
}

puranjayK · 2021-12-18T18:23:13Z

Hi @f-odhiambo, I would like to work on this issue
Could you please assign it to me

f-odhiambo · 2021-12-19T21:49:00Z

Hi @f-odhiambo, I would like to work on this issue Could you please assign it to me

Kindly tag me to the PR or leave a comment once a PR has been raised for this

puranjayK · 2021-12-21T21:19:15Z

@f-odhiambo @jingtang10 could you please help me with the questionnaire of the Location widget.

f-odhiambo · 2021-12-24T15:21:51Z

@f-odhiambo @jingtang10 could you please help me with the questionnaire of the Location widget.

Here you go http://turn-fhir.smartregister.org/fhir/Questionnaire/1922. You can add the widget to this questionnaire

f-odhiambo · 2022-01-05T08:22:06Z

Hey, @puranjayK Any progress update on this ? Perhaps we can link up on this sometime this week if available for more details. Let me know

f-odhiambo · 2022-01-13T09:42:15Z

@puranjayK Any progress update on this?

puranjayK · 2022-01-13T12:15:22Z

@puranjayK Any progress update on this?

Sorry I couldnt work on this, as the covid situation got worse in my country.
I am having issues on how to make this widget and how the questionnaire is to be used

PallaviGanorkar · 2022-02-04T11:51:09Z

@jingtang10 @Tarun-Bhardwaj As discussed need to hold this issue for more requirement details.

f-odhiambo · 2022-02-04T12:12:41Z

HI @PallaviGanorkar , Are you going to be picking this issue ?

MnCSSJ4x · 2022-02-15T15:35:39Z

Hello I am new to contribution and would like to contribute to this issue if no one is on it.

f-odhiambo · 2022-02-17T19:19:16Z

Hi @MnCSSJ4x,Thanks for this , how can we connect to have a brief on this issue, can we ?
CC @FikriMilano

MnCSSJ4x · 2022-02-18T05:56:40Z

we can connect via mail : xxxxx
or if there is a slack channel please share an invite

MnCSSJ4x · 2022-03-02T11:27:26Z

@FikriMilano I was planning to follow the sample format mentioned until and unless there is some limitation

FikriMilano · 2022-03-02T12:10:44Z

Alright, sounds good for me.
Thanks for the feedback @MnCSSJ4x

f-odhiambo · 2022-03-08T07:45:02Z

Hi @MnCSSJ4x , how is the progress here ?
CC @FikriMilano

MnCSSJ4x · 2022-03-08T07:47:29Z

@f-odhiambo
I am having my semester exams this week. Will definitely address the coding part of the solution next week
@FikriMilano can you provide me how you set up the environment locally to test ?

FikriMilano · 2022-03-08T08:03:47Z

@MnCSSJ4x you can just simply fork the repo, build the project then try to run the demo apps

f-odhiambo · 2022-04-06T14:17:47Z

@MnCSSJ4x Any progress made on this ticket?

f-odhiambo · 2022-08-27T18:44:37Z

@Tarun-Bhardwaj I think we can close this issue as it had been implemented on FHIR Core opensrp/fhircore#1536

fredhersch · 2022-08-30T07:06:34Z

Thanks @f-odhiambo - would it be worth merging this back into the SDK? @jingtang10

f-odhiambo · 2022-08-30T12:55:19Z

Thanks @f-odhiambo - would it be worth merging this back into the SDK? @jingtang10

We can have a discussion on this , happy to elaborate more on the solution we took

dubdabasoduba · 2023-11-06T10:37:12Z

@ageryck I think you can re-open this ticket for the GPS picker work.

ageryck · 2023-11-09T07:39:52Z

@jingtang10 this can be re-assigned since the implementation in the attached PR was something different

LZRS · 2023-11-29T08:29:46Z

@f-odhiambo @f-odhiambo I had a suggestion of maybe using a normal Questionnaire item of type string with a custom extension to render the widget

 {
          "linkId": "Location widget",
          "type": "string",
          "text": "Record GPS Location",
          "required": true,
          "extension": [
            {
              "url": "https://github.com/google/android-fhir/StructureDefinition/questionnaire-itemControl",
              "valueCodeableConcept": {
                "coding": [
                  {
                    "system": "https://github.com/google/android-fhir/questionnaire-item-control",
                    "code": "location-widget"
                  }
                ]
              }
            }
          ]
        }

and to render, instead of having it as single "record gps location", maybe have it render similar to the datepicker populating the textview with comma-separated latitude, longitude, altitude. This way we would probably still be able to use the already implemented utilities for example, adding extensions for help, attachment, translations and also show validation error incase field is required

cc: @ageryck @FikriMilano @dubdabasoduba

LZRS · 2023-12-15T09:27:38Z

After reviewing the above implementation idea, we felt it may have had deficiencies of may be not being able to separate between latitude and longitude in consistent way. And so, with the help of the fhir org team, we had another idea that would be viable, to use a Questionnaire item of type group. The Questionnaire item would have a custom extension to represent location-widget and also have child items of type string with custom extensions to specify latitude, longitude and altitude - these would be used in the ui to render and populate the coordinates.

Essentially, it would look like

 {
          "linkId": "location-widget",
          "type": "group",
          "extension": [
            {
              "url": "https://github.com/google/android-fhir/StructureDefinition/questionnaire-itemControl",
              "valueCodeableConcept": {
                "coding": [
                  {
                    "system": "https://github.com/google/android-fhir/questionnaire-item-control",
                    "code": "location-widget"
                  }
                ]
              }
            }
          ],
        "item": [
          {
            "linkId": "latitude",
            "type": "string",
            "required": true,
            "readOnly": true,
            "extension": [
              {
                "url": "gps-coordinate",
                "value": "latitude"
              }
            ]
          },
          {
            "linkId": "longitude",
            "type": "string",
            "required": true,
            "readOnly": true,
            "extension": [
              {
                "url": "gps-coordinate",
                "value": "longitude"
              }
            ]
          }
        ]
        }

@jingtang10 would love to hear what you think

cc @f-odhiambo @ageryck

jingtang10 · 2023-12-15T16:55:50Z

I think defining custom widgets (together with custom extensions) in the SDC library is a great approach. This is fine.

The important thing is documentation and making sure people using your questionnaires are aware of the extensions you define otherwise your questionnaire will not be usable.

Be good to share this with the fhir chat community as well, especially to get grahame and lloyd's opinion.

dubdabasoduba · 2023-12-15T17:29:01Z

After reviewing the above implementation idea, we felt it may have had deficiencies of may be not being able to separate between latitude and longitude in consistent way. And so, with the help of the fhir org team, we had another idea that would be viable, to use a Questionnaire item of type group. The Questionnaire item would have a custom extension to represent location-widget and also have child items of type string with custom extensions to specify latitude, longitude and altitude - these would be used in the ui to render and populate the coordinates.

Essentially, it would look like

 {
          "linkId": "location-widget",
          "type": "group",
          "extension": [
            {
              "url": "https://github.com/google/android-fhir/StructureDefinition/questionnaire-itemControl",
              "valueCodeableConcept": {
                "coding": [
                  {
                    "system": "https://github.com/google/android-fhir/questionnaire-item-control",
                    "code": "location-widget"
                  }
                ]
              }
            }
          ],
        "item": [
          {
            "linkId": "latitude",
            "type": "string",
            "required": true,
            "readOnly": true,
            "extension": [
              {
                "url": "gps-coordinate",
                "value": "latitude"
              }
            ]
          },
          {
            "linkId": "longitude",
            "type": "string",
            "required": true,
            "readOnly": true,
            "extension": [
              {
                "url": "gps-coordinate",
                "value": "longitude"
              }
            ]
          }
        ]
        }

@jingtang10 would love to hear what you think

cc @f-odhiambo @ageryck

@LZRS how does this look on the QR? Do you mind sharing a sample?

LZRS · 2023-12-18T12:04:28Z

After reviewing the above implementation idea, we felt it may have had deficiencies of may be not being able to separate between latitude and longitude in consistent way. And so, with the help of the fhir org team, we had another idea that would be viable, to use a Questionnaire item of type group. The Questionnaire item would have a custom extension to represent location-widget and also have child items of type string with custom extensions to specify latitude, longitude and altitude - these would be used in the ui to render and populate the coordinates.
Essentially, it would look like

 {
          "linkId": "location-widget",
          "type": "group",
          "extension": [
            {
              "url": "https://github.com/google/android-fhir/StructureDefinition/questionnaire-itemControl",
              "valueCodeableConcept": {
                "coding": [
                  {
                    "system": "https://github.com/google/android-fhir/questionnaire-item-control",
                    "code": "location-widget"
                  }
                ]
              }
            }
          ],
        "item": [
          {
            "linkId": "latitude",
            "type": "string",
            "required": true,
            "readOnly": true,
            "extension": [
              {
                "url": "gps-coordinate",
                "value": "latitude"
              }
            ]
          },
          {
            "linkId": "longitude",
            "type": "string",
            "required": true,
            "readOnly": true,
            "extension": [
              {
                "url": "gps-coordinate",
                "value": "longitude"
              }
            ]
          }
        ]
        }

@jingtang10 would love to hear what you think
cc @f-odhiambo @ageryck

@LZRS how does this look on the QR? Do you mind sharing a sample?

The QuestionnaireResponse would probably look like this

{
  "linkId": "location-widget",
  "item": [
    {
      "linkId": "latitude",
      "answer": [
        {
          "valueString": "41.40338"
        }
      ]
    },
    {
      "linkId": "longitude",
      "answer": [
        {
          "valueString": "2.17403"
        }
      ]
    }
  ]
}

f-odhiambo added the type:enhancement New feature or request label Sep 28, 2021

f-odhiambo mentioned this issue Sep 28, 2021

CHW/ANC - Add location widget opensrp/fhircore#520

Closed

pld added data-capture good first issue Good for newcomers labels Sep 28, 2021

f-odhiambo closed this as completed Oct 12, 2021

f-odhiambo reopened this Oct 12, 2021

f-odhiambo mentioned this issue Dec 16, 2021

Add Location Widget (a.k.a GPS picker) to FHIR Core opensrp/fhircore#880

Closed

f-odhiambo assigned puranjayK Dec 19, 2021

f-odhiambo changed the title ~~Add location widget~~ Add location mapping widget Jan 26, 2022

f-odhiambo unassigned puranjayK Feb 1, 2022

Tarun-Bhardwaj assigned PallaviGanorkar Feb 3, 2022

f-odhiambo unassigned PallaviGanorkar Feb 7, 2022

f-odhiambo closed this as completed Aug 27, 2022

fredhersch added this to Android FHIR SDK Aug 29, 2022

fredhersch moved this to Backlog in Android FHIR SDK Aug 29, 2022

Tarun-Bhardwaj removed the To be triaged label Sep 6, 2022

Tarun-Bhardwaj moved this from Backlog to Complete in Android FHIR SDK Sep 12, 2022

Tarun-Bhardwaj removed this from Android FHIR SDK Sep 13, 2022

Tarun-Bhardwaj added this to Android FHIR SDK Sep 16, 2022

Tarun-Bhardwaj moved this to Backlog in Android FHIR SDK Sep 16, 2022

Tarun-Bhardwaj moved this from Backlog to Complete in Android FHIR SDK Sep 21, 2022

f-odhiambo reopened this Nov 7, 2023

github-project-automation bot moved this from Complete to New in Android FHIR SDK Nov 7, 2023

LZRS mentioned this issue Nov 28, 2023

Support location widget to get current location #2341

Merged

7 tasks

aditya-07 closed this as completed in #2341 Feb 7, 2024

github-project-automation bot moved this from New to Complete in Android FHIR SDK Feb 7, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add location mapping widget #800

Add location mapping widget #800

f-odhiambo commented Sep 28, 2021 •

edited

Loading

jingtang10 commented Sep 29, 2021

f-odhiambo commented Oct 8, 2021

f-odhiambo commented Oct 12, 2021 •

edited

Loading

puranjayK commented Dec 18, 2021

f-odhiambo commented Dec 19, 2021 •

edited

Loading

puranjayK commented Dec 21, 2021

f-odhiambo commented Dec 24, 2021 •

edited

Loading

f-odhiambo commented Jan 5, 2022

f-odhiambo commented Jan 13, 2022

puranjayK commented Jan 13, 2022

PallaviGanorkar commented Feb 4, 2022

f-odhiambo commented Feb 4, 2022

MnCSSJ4x commented Feb 15, 2022

f-odhiambo commented Feb 17, 2022

MnCSSJ4x commented Feb 18, 2022 •

edited by f-odhiambo

Loading

MnCSSJ4x commented Mar 2, 2022

FikriMilano commented Mar 2, 2022

f-odhiambo commented Mar 8, 2022

MnCSSJ4x commented Mar 8, 2022

FikriMilano commented Mar 8, 2022

f-odhiambo commented Apr 6, 2022

f-odhiambo commented Aug 27, 2022

fredhersch commented Aug 30, 2022

f-odhiambo commented Aug 30, 2022

dubdabasoduba commented Nov 6, 2023

ageryck commented Nov 9, 2023

LZRS commented Nov 29, 2023 •

edited

Loading

LZRS commented Dec 15, 2023 •

edited

Loading

jingtang10 commented Dec 15, 2023

dubdabasoduba commented Dec 15, 2023

LZRS commented Dec 18, 2023

Add location mapping widget #800

Add location mapping widget #800

Comments

f-odhiambo commented Sep 28, 2021 • edited Loading

jingtang10 commented Sep 29, 2021

f-odhiambo commented Oct 8, 2021

f-odhiambo commented Oct 12, 2021 • edited Loading

puranjayK commented Dec 18, 2021

f-odhiambo commented Dec 19, 2021 • edited Loading

puranjayK commented Dec 21, 2021

f-odhiambo commented Dec 24, 2021 • edited Loading

f-odhiambo commented Jan 5, 2022

f-odhiambo commented Jan 13, 2022

puranjayK commented Jan 13, 2022

PallaviGanorkar commented Feb 4, 2022

f-odhiambo commented Feb 4, 2022

MnCSSJ4x commented Feb 15, 2022

f-odhiambo commented Feb 17, 2022

MnCSSJ4x commented Feb 18, 2022 • edited by f-odhiambo Loading

MnCSSJ4x commented Mar 2, 2022

FikriMilano commented Mar 2, 2022

f-odhiambo commented Mar 8, 2022

MnCSSJ4x commented Mar 8, 2022

FikriMilano commented Mar 8, 2022

f-odhiambo commented Apr 6, 2022

f-odhiambo commented Aug 27, 2022

fredhersch commented Aug 30, 2022

f-odhiambo commented Aug 30, 2022

dubdabasoduba commented Nov 6, 2023

ageryck commented Nov 9, 2023

LZRS commented Nov 29, 2023 • edited Loading

LZRS commented Dec 15, 2023 • edited Loading

jingtang10 commented Dec 15, 2023

dubdabasoduba commented Dec 15, 2023

LZRS commented Dec 18, 2023

f-odhiambo commented Sep 28, 2021 •

edited

Loading

f-odhiambo commented Oct 12, 2021 •

edited

Loading

f-odhiambo commented Dec 19, 2021 •

edited

Loading

f-odhiambo commented Dec 24, 2021 •

edited

Loading

MnCSSJ4x commented Feb 18, 2022 •

edited by f-odhiambo

Loading

LZRS commented Nov 29, 2023 •

edited

Loading

LZRS commented Dec 15, 2023 •

edited

Loading