Resource Creation using POST http verb (SingleResourcePost)

[santosh-pingle]

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).

Fixes #2440

Description
The resource is created locally, and the HTTP POST verb is used to synchronize the resource with the FHIR server. In return, the server sends a response containing the resource with the newly assigned resource ID. Subsequently, the local database is updated with the provided resource.

Upload strategy : SingleResourcePost
Update the resource with the received resourceId in the local database
Update the resource with the received meta data in the local database
Update the resource with the received resource json string in the local database

Update the resource with the received reference id in the local database.

Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?

Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)

Screenshots (if applicable)

Checklist

• I have read and acknowledged the Code of conduct.
• I have read the Contributing page.
• I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
• I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
• I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
• I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
• I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

[dubdabasoduba]

@santosh-pingle How is this going to work? Are we making it the default behaviour for all CREATEs.

Right now if you POST to a HAPI server, the server assigns the resource its own id.

e.g posting the following resource

{
  "resourceType": "List",
  "id": "af17fe86-561a-44b0-84d3-5e75c753f6f8",
  "meta": {
    "versionId"  : "1"                            ,
    "lastUpdated": "2024-03-13T15:41:42.808+00:00",
    "source"     : "#fd2dc30247cf61b8"
  },
  "identifier": [
    {"use": "official", "value": "f39c5f68-ab0f-4ae5-a9e2-47b0beb73d8e"}
  ],
  "status": "current",
  "code": {
    "coding": [
      {
        "system" : "http://smartregister.org/",
        "code"   : "22138876"                 ,
        "display": "Supply Inventory List"
      }
    ],
    "text": "Supply Inventory List"
  }
}

will result in

{
  "resourceType": "List",
  "id": "1759",
  "meta": {
    "versionId"  : "1"                            ,
    "lastUpdated": "2024-04-04T09:09:05.431+00:00",
    "source"     : "#fd2dc30247cf61b8"
  },
  "identifier": [
    {"use": "official", "value": "f39c5f68-ab0f-4ae5-a9e2-47b0beb73d8e"}
  ],
  "status": "current",
  "code": {
    "coding": [
      {
        "system" : "http://smartregister.org/",
        "code"   : "22138876"                 ,
        "display": "Supply Inventory List"
      }
    ],
    "text": "Supply Inventory List"
  }
}

The above behaviour is going to distort the resource references for any resources created on the mobile application

cc: @ellykits @qiarie @ndegwamartin

[dubdabasoduba]

@santosh-pingle How is this going to work? Are we making it the default behaviour for all CREATEs.

Right now if you POST to a HAPI server, the server assigns the resource its own id.

e.g posting the following resource

{
  "resourceType": "List",
  "id": "af17fe86-561a-44b0-84d3-5e75c753f6f8",
  "meta": {
    "versionId"  : "1"                            ,
    "lastUpdated": "2024-03-13T15:41:42.808+00:00",
    "source"     : "#fd2dc30247cf61b8"
  },
  "identifier": [
    {"use": "official", "value": "f39c5f68-ab0f-4ae5-a9e2-47b0beb73d8e"}
  ],
  "status": "current",
  "code": {
    "coding": [
      {
        "system" : "http://smartregister.org/",
        "code"   : "22138876"                 ,
        "display": "Supply Inventory List"
      }
    ],
    "text": "Supply Inventory List"
  }
}

will result in

{
  "resourceType": "List",
  "id": "1759",
  "meta": {
    "versionId"  : "1"                            ,
    "lastUpdated": "2024-04-04T09:09:05.431+00:00",
    "source"     : "#fd2dc30247cf61b8"
  },
  "identifier": [
    {"use": "official", "value": "f39c5f68-ab0f-4ae5-a9e2-47b0beb73d8e"}
  ],
  "status": "current",
  "code": {
    "coding": [
      {
        "system" : "http://smartregister.org/",
        "code"   : "22138876"                 ,
        "display": "Supply Inventory List"
      }
    ],
    "text": "Supply Inventory List"
  }
}

The above behaviour is going to distort the resource references for any resources created on the mobile application

cc: @ellykits @qiarie @ndegwamartin

This was clarified on the SDK dev call. I think this is a good addition

[santosh-pingle]

@santosh-pingle How is this going to work? Are we making it the default behaviour for all CREATEs.

Right now if you POST to a HAPI server, the server assigns the resource its own id.

e.g posting the following resource

{
  "resourceType": "List",
  "id": "af17fe86-561a-44b0-84d3-5e75c753f6f8",
  "meta": {
    "versionId"  : "1"                            ,
    "lastUpdated": "2024-03-13T15:41:42.808+00:00",
    "source"     : "#fd2dc30247cf61b8"
  },
  "identifier": [
    {"use": "official", "value": "f39c5f68-ab0f-4ae5-a9e2-47b0beb73d8e"}
  ],
  "status": "current",
  "code": {
    "coding": [
      {
        "system" : "http://smartregister.org/",
        "code"   : "22138876"                 ,
        "display": "Supply Inventory List"
      }
    ],
    "text": "Supply Inventory List"
  }
}

will result in

{
  "resourceType": "List",
  "id": "1759",
  "meta": {
    "versionId"  : "1"                            ,
    "lastUpdated": "2024-04-04T09:09:05.431+00:00",
    "source"     : "#fd2dc30247cf61b8"
  },
  "identifier": [
    {"use": "official", "value": "f39c5f68-ab0f-4ae5-a9e2-47b0beb73d8e"}
  ],
  "status": "current",
  "code": {
    "coding": [
      {
        "system" : "http://smartregister.org/",
        "code"   : "22138876"                 ,
        "display": "Supply Inventory List"
      }
    ],
    "text": "Supply Inventory List"
  }
}

The above behaviour is going to distort the resource references for any resources created on the mobile application

cc: @ellykits @qiarie @ndegwamartin

We have kept existing DefaultConsolidator as it is.

[MJ1998]

Checkout this PR which added bunch of stuffs for POST upload strategy.

[santosh-pingle]

Checkout this PR which added bunch of stuffs for POST upload strategy.

Yes, I am using the core logic as it is. Only delta changes are added on top of it to achieve the end-to-end use case for resource consolidation.

[MJ1998]

Thanks this looks good now!
Can we add few integration tests as well ? Maybe in FhirEngineImplTest ?

[MJ1998]

LGTM. One nit.

Addressed review comments, reviewed and approved by code owner @MJ1998, hence dismissing review.