openIMIS tblClaim resource (FHIR Claim / ClaimResponse)
List of content:
Description:
In the current version are mapped fields required by uspUpdateClaimFromPhone database stored procedure (SP) which is used by python claim service to submitting the claim.
Only GET and POST HTTP methods are currently exposed because the current version is focused on the claim submitting. The GET operation can be used to fetch information about all claim (or a specific one) and the POST operation can be used to submit the claim (note: response for the request is the OperationOutcome on failure and ClaimResponse on successful).
Notes / Assumptions:
The current version of mapping will be focused on aspects of claiming.
To fully mapped the claim probably need to be used two different FHIR resources. Claim - contains base information about the claim (request), ClaimResponse - contains information which is the outcome of processing claim (response).
The claim code is used (for Claim and ClaimResponse resource) as the resource primary key because of the uspUpdateClaimFromPhone didn't return the value of id a new claim
FHIR resources:
Request | |
Response |
Fields mapping:
Table legend:
Color | Description |
---|---|
Mapped - the final choice, the most suitable choice | |
Need to be found the best place for the field (not mapped currently) | |
Currently not important - not mapped |
Claim mapping:
OpenIMIS field | DB type | Request or response | FHIR field | Description | Note | STPH | Mapping status |
ClaimID | PK | Request | claim.Identifier | this isn't required, most important is the ClaimCode (see below) but FHIR claim can have multiple identifiers | I would include ClaimUUID into the Claim instead of ClaimID. | This is the Database ID and should be used only internally | |
ClaimUUID | uniqueidentifier | Response | claim.Identifier | The unique identifier used as PK for FHIR | Will be added when will be available in the python claim module |