This repository has been archived by the owner on May 7, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 114
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
5 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -304,9 +304,10 @@ fields: | |
} | ||
note: > | ||
<ul> | ||
<li>The default value is boolean value 'true'.</li> | ||
<li>When the value is 'true' the payment will be posted across existing self-pay balances.</li> | ||
<li>When the value is 'false' the system creates a new recurring encounter and posts the payment to the new self pay balance.</li> | ||
<li>Only supported when payment or adjustment is targeted at an Encounter</li> | ||
<li>The default value is the boolean value 'true'.</li> | ||
<li>When the value is 'true' the payment will be posted across existing financial activity with any outstanding balances using FIFO logic. If there is no existing financial activity, the system will create a new financial activity for the current month and post the payment. If there is an existing financial activity with no outstanding balance, the system will post the payment to the latest month's financial activity.</li> | ||
This comment has been minimized.
Sorry, something went wrong. |
||
<li>When the value is 'false' the system will post the payment to the current month's financial activity given it exists. If not, the system creates a new financial activity for the current month and posts the payment.</li> | ||
This comment has been minimized.
Sorry, something went wrong.
alexbeckner1
|
||
<li>Only supported for the Payment Transaction Type with target as Encounter</li> | ||
<li>This extension is only supported for recurring encounter and not other types of encounters like inpatient, outpatient, etc.</li> | ||
This comment has been minimized.
Sorry, something went wrong.
alexbeckner1
|
||
</ul> | ||
url: https://fhir-ehr.cerner.com/r4/StructureDefinition/apply-first-in-first-out?_format=json |
When the value is 'true' the system posts the payment across existing financial activity with any outstanding balances using FIFO logic. If there is no existing financial activity, the system creates a new financial activity for the current month and posts the payment to the new financial activity. If there is an existing financial activity with no outstanding balance, the system will post the payment to the latest month's financial activity.