Back To Index  <<  Back To Issues

 (epsos-issue-52) Cardinality/nullFlavor for address (parts)
Change Request (issue id 2.16.840.1.113883.2.4.3.11.60.22.6.52)
Last assignment to Giorgio Cangioli

Issue Cardinality/nullFlavor for address (parts)
Id epsos-issue-52
Type Change Request
Status  Open, assigned
Priority normal
arrowright Assignment to Giorgio Cangioli (id#5) on 2013‑12‑02 13:33:24
  Author assigned by Alexander Henket (id#4)
tracking Tracking 2013‑12‑02 13:31:47 - status: Open
  Author Alexander Henket
Description

In "epSOS_D3.9.1_Appendix_B1_B2_Implementation_v1.4_20110725.pdf" it would appear that addresses are overstated and suffer from some copy/paste problems. You are currently required to either state no address parts or every single mentioned address part with either a value or a nullFlavor (not stated which nullFlavor). Also every address part may appear 1..* R, including city, state, and country. This leads to fragments like:

         <addr use="H">
            <state nullFlavor="NI"/>
            <city>MILANO</city>
            <country>IT</country>
            <state>ZH</state>
            <city>ROTTERDAM</city>
            <country>NL</country>
            <postalCode nullFlavor="UNK"/>
         </addr>

I.e. multiple types of NULL and multiple colliding address parts. What is the reason behind this? Any addr specification we have encountered in any context has said that unknown address(parts/es) should just be omitted, and with the exception of streetAddressLine no other parts should be use more than once.