Foundational support of DFT_P03 message and IN1 segment. (Coverage, Related Person, etc)
cragun47 opened this issue · comments
Brian Cragun commented
Foundational support for IN1 mapped to Coverage
- Create
Coverage
template- Map
coverage.identifier
- Map
coverage.status
- Map
coverage.payor
, create a referenced Organization. - Map
coverage.beneficiary
, reference Patient created from PID - Map
coverage.class
- Map
coverage.order
- Map
coverage.subscriberId
- Map
coverage.relatedPerson
, create a referenced RelatedPerson - Map
coverage.relationship
(to the RelatedPerson) - Map reference to Patient when relationship is SEL (self)
- Map
- Create
Class
template - Create
RelatedPerson
template- Map
relatedPerson.name
- Map
relatedPerson.brithdate
- Map
relatedPerson.address
- Map
relatedPerson.gender
- Map
relatedPerson.relationship
- Map
relatedPerson.identifier
- Map
- Map to the referenced Organization:
- Map
organization.identifier
- Map
organization.name
- Map
organization.contact
and associated detail: name, period, telecom - Map
organization.address
and associated detail including period
- Map
Initial support for DFT_P03 message type. Handle:
MSH
PID
to PatientPV1
to EncounterIN1
to CoverageORC
to ServiceRequestOBX
to Observation
Note FT1 is not currently utilized or supported.
Brian Cragun commented
This was included in Release 1.0.15