Understandingthe Implementation Approach for Dynamic Fields in OHI Integration Points
(Doc ID 2504511.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Health Insurance Claims Adjudication - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
What mechanism does OHI use to support the addition of dynamic fields for parsing payloads and payload generation for its integration points?
Example: There is a single valued, non-time valid dynamic field on working copy and CTR. How does CCIN and CCOUT integration point on OHI adapt to it?
For CCIN: When OHI receives the payload it parses it and checks which and how dynamic field are in OHI before persisting the claim?
For CCOUT: is CCOUT response built based on table structure for CTR? Then it checks the mapping of table column names with dynamic field definition to map data under appropriate attributes and elements configured in OHI?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document