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	Claim
Response	ClaimResponse

Fields mapping:

Table legend:

Color	Description

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		mapped
InsureeID	FK(tblInsuree)	Request	claim.patient - Reference(Patient)	The subject of the Products and Services	We can represent the insuree as the FHIR patient resource but the most important is claim.patient.identifier	claim.patient.identifier	mapped
ClaimCode	nvarchar	Request	claim.Identifier	Claim number		OK	mapped
DateFrom	smalldatetime	Request	claim.billablePeriod	Period for charge submission		OK	mapped
DateTo	smalldatetime	Request	claim.billablePeriod	Period for charge submission		OK	mapped
ICDID	FK(tblICDCodes)	Request	claim.diagnosis	List of Diagnosis	If ICD is some fixed set of coded value then we can use the CodeableCondept to describe this. The sequence field can be used to create an order of diagnosis.	OK	mapped
ClaimStatus	tinyint	Response	claimResponse.outcome	Default value: 2; 1 - rejected 2 - entered 4 - checked 8 - processed 16 - valuated	Used the FHIR codeable concept (code = imis_status, text = displayed status)	Can be also a combination of claimResponse.status and claimResponse.outcome but limited in values. Extension required?	mapped
Adjuster	FK(tblUsers)	Request	claim.provider - Reference(Practitioner)	Responsible provider	I'm not sure if this field is used, all records created by me have null values in that field.	Only reference to openIMIS user.
Adjustment	ntext	Response	claimResponse.payment.adjustmentReason		Used FHIR adjustmentReason because of the IMIS Adjustment is text.	claimResponse.payment.adjustment	mapped
Claimed	decimal	Request	claim.total	Total claim cost		OK	mapped
Approved	decimal	Response	claimResponse.totalBenefit			OK	mapped
Reinsured	decimal	Response			If needed we can create the FHIR extension.
Valuated	decimal	Response			If needed we can create the FHIR extension.
DateClaimed	date	Request	claim.created	default: getDate()		OK	mapped
DateProcessed	smalldatetime	Response	claimResponse.payment.date		claimResponse.created is used is the request date	If different endpoint to claimResponse, claimResponse.created will be the request date. Maybe claimResponse.payment.date	mapped
Feedback	bit			default value: 0		No need. To see if replaced by FeedbackID
FeedbackID	FK(tblFeedback)	Response	claimResponse.communicationRequest	default value: 0		claimResponse.communicationRequest	mapped
Explanation	ntext	Request	claim.information.valueString	Additional Data or supporting information		OK	mapped
FeedbackStatus	tinyint	-		default value: 1 1 - idle 2 - not selected 4 - selected for feedback 8 - delicered 16 - by passed else select status	This field probably is used only by the OpenIMIS and isn't requirement by external systems.	Only used internally
ReviewStatus	tinyint	-		default value: 1 1 - idle 2 - not selected 4 - selected for review 8 - reviewed 16 - by passed else select status	This field probably is used only by the OpenIMIS and isn't requirement by external systems.	Only used internally
ApprovalStatus	tinyint	-		default value: 1;	Probably not used field
RejectionReason	tinyint	Response	claimResponse.error	default value: 0		In Web App we have the rejection reason for each Item and Service in a Claim. We should provide these reasons.	mapped
ValidityFrom	datetime	-		Audit information. More information can be found here (on page 113): Web application - Functional Design Specification.pdf	This information are valuable for OpenIMIS but probably not required by external systems.
ValidityTo	datetime	-
LegacyID	int	-
AuditUserID	int	-
ValidityFromReview	datetime	Response			I'm not sure if this information are valuable for external systems. If needed we can try to use the claimResponse.processNote or add the FHIR extensions.	I don't think this information is valuable for external systems. It's only used internally.
ValidityToReview	datetime	Response
AuditUserIDReview	int	Response
RowID	timestamp	-			I'm not sure but this is probably some unique value used to distinguish database rows. Probably not useful for external systems.	Not used by external systems.
HFID	FK(tblHF)	Request	claim.facility - Reference(Location)	Servicing Facility		Could also be Claim.organization
RunID	FK(tblBatchRun)	-			This is probably useful only for the internal system not for external systems. If needed add the FHIR extension can be considered.	Not used by external systems.
AuditUserIDSubmit	int	Response			I'm not sure if this information are valuable for external systems. If needed we can try to use the claimResponse.processNote or add the FHIR extensions.
AuditUserIDProcess	int	Response
SubmitStamp	datetime	Response

openIMIS tblClaim resource (FHIR Claim / ClaimResponse)