You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2017. It is now read-only.
We have some CCD extracts that contain both C32 and CCDA template Id's in the document header. The document contents are actually a CCDA format, however since the C32 template Id appears first in the header, BB assumes the doc is a C32. I would think that an option to ignore the header and parse each section according to the section template Id alone would solve this issue. Otherwise maybe an option to force BB to use a template Id regardless of what is contained in the document header would also suffice. Basically skip the 'detect()' method. I believe that an originating system should only specify one type in the header but I have read about some including both regardless so this is not just an isolated incident.
This is the header from one of our files:
<templateId root="2.16.840.1.113883.10.20.1" />
<templateId root="2.16.840.1.113883.10.20.3" assigningAuthorityName="HL7/CDT Header" />
<templateId root="2.16.840.1.113883.3.88.11.32.1" assigningAuthorityName="HL7/CDT Header" />
<templateId root="1.3.6.1.4.1.19376.1.5.3.1.1.1" assigningAuthorityName="HL7/CDT Header" />
<templateId root="2.16.840.1.113883.10.20.22.1.1" assigningAuthorityName="HL7/CCD 1.1" />
<templateId root="2.16.840.1.113883.10.20.22.1.2" assigningAuthorityName="HL7/CCD 1.1" />
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have some CCD extracts that contain both C32 and CCDA template Id's in the document header. The document contents are actually a CCDA format, however since the C32 template Id appears first in the header, BB assumes the doc is a C32. I would think that an option to ignore the header and parse each section according to the section template Id alone would solve this issue. Otherwise maybe an option to force BB to use a template Id regardless of what is contained in the document header would also suffice. Basically skip the 'detect()' method. I believe that an originating system should only specify one type in the header but I have read about some including both regardless so this is not just an isolated incident.
This is the header from one of our files:
<templateId root="2.16.840.1.113883.10.20.1" />
<templateId root="2.16.840.1.113883.10.20.3" assigningAuthorityName="HL7/CDT Header" />
<templateId root="2.16.840.1.113883.3.88.11.32.1" assigningAuthorityName="HL7/CDT Header" />
<templateId root="1.3.6.1.4.1.19376.1.5.3.1.1.1" assigningAuthorityName="HL7/CDT Header" />
<templateId root="2.16.840.1.113883.10.20.22.1.1" assigningAuthorityName="HL7/CCD 1.1" />
<templateId root="2.16.840.1.113883.10.20.22.1.2" assigningAuthorityName="HL7/CCD 1.1" />
The text was updated successfully, but these errors were encountered: