|
|
Class steward is Patient Administration
A charge, credit, or adjustment to charges in a patient's billing account.
An alternate description of the transaction.
|FT1^9^00363^Transaction Description - Alt|
Explanatory text concerning a financial transaction.
|FT1^8^00362^Transaction Description|
The transaction amount derived from multiplying the unit amount by the number of units.
OpenIssue: Note this is a derived attribute as described. Is MnM OK with this?
|FT1^11^00365^Transaction Amount - Extended|
A code depicting the fee schedule used for this financial transaction.
|FT1^17^00370^Fee Schedule|
The amount of the financial transaction that is applicable to the associated Healthcare benefit plan.
|FT1^15^00369^Insurance Amount|
The posting date of the financial transaction.
|FT1^5^00359^Transaction Posting Date|
transaction quantity.
OpenIssue: This attribute is not defined either here or in Version 2.3. It may be "number of units" but that is only a guess.
|FT1^10^00364^Transaction Quantity|
A unique identifier assigned to the batch in which this transaction belongs.
|FT1^3^00357^Transaction Batch ID|
A code depicting the financial action covered in the transaction.
|FT1^7^00361^Transaction Code|
The date of the transaction.
|FT1^4^00358^Transaction Date|
A identifier assigned to the transaction for control purposes.
|FT1^2^00356^Transaction ID| |UB2^12^00564^Document Control Number|
A code depicting the transaction type (e.g., credit, charge, payment, adjustment, ...).
|FT1^6^00360^Transaction Type|
The amount associated with one transaction unit.
OpenIssue: Note that the class carries no definitions or attributes to indicate what a unit is or what the kind (cd) for the unit should be.
|FT1^12^00366^Transaction Amount - Unit|
The unit price of transaction. The cost of a single item.
OpenIssue: Note that the class carries no definitions to indicate what a unit is or what the kind (cd) for the unit should be.
|FT1^22^00374^Unit Cost|
OpenIssue: Is not the person who enters a financial transaction in a specific role? On behalf of an organization? When very loosely coupled systems exchange messages, they'll have to specify the role and accountability, won't they?
OpenIssue: Association names are not descriptive of what this association means. There is currently no way to describe fees for services in a master file. The issues of fees, fee schedule and their relationship to actual charges need to be modeled. Or does the assoication between RIM092.Master_service and Coverage_item allow to assign different fees to the same master service?