[CYPRESS-178] Cypress 2.3.0 reports error for Family Member value set OID in Diagnosis Family History template Created: 08/02/13  Updated: 06/20/18  Resolved: 12/12/13

Status: Closed
Project: CYPRESS Issue Tracker
Component/s: None

Type: Bug/Issue Priority: Minor
Reporter: Jon Salmon (Inactive) Assignee: Robert Dingwell (Inactive)
Resolution: Delivered Votes: 0
Labels: QRDA-I

Solution: Fixed in Cypress 2.4.1
Previous Issue Type: Implementation Problem

 Description   

Consider the uploading of a QRDA Category I file that contains an entry for a Diagnosis Family History template (2.16.840.1.113883.10.20.24.3.12)
and specifies the OID for the Family Member value set (2.16.840.1.113883.1.11.19579) in the sdtc:valueSet attribute for the relatedSubject. For example:

<relatedSubject classCode="PRS">
	<code code="FTH" codeSystem="2.16.840.1.113883.5.111" codeSystemName="ROLECODE" displayName="Father" sdtc:valueSet="2.16.840.1.113883.1.11.19579"/>
</relatedSubject>

Given such a file, Cypress 2.3.0 reports the following error:

The valueset 2.16.840.1.113883.1.11.19579 declared in the document cannot be found

This value set is specifically referenced in the QRDA Category I spec:

ii. This relatedSubject SHALL contain exactly one [1..1] code (CONF:15246).
1. This code SHALL contain exactly one [1..1] @code, which SHOULD be selected from ValueSet Family Member Value Set 2.16.840.1.113883.1.11.19579 DYNAMIC (CONF:15247).

Also per the spec, all coded values are allowed to specify the sdtc:valueSet attribute:

b. Coded fields MAY contain the @sdtc:valueSet extension to reference the value set from which the supplied code was drawn. (CONF:16859).

This value set is not included in the current value set downloads from VSAC so perhaps it should be added. (I will submit that as a CQM issue if you like.) Regardless, as it is clearly acknowledged and allowed per the QRDA spec, its presence should not result in an error in Cypress.

This affects EP measures CMS61v3 and CMS64v3.

 Comments   
Comment by Robert Dingwell (Inactive) [ 09/17/13 ]

Jon,

This should have been corrected in Cyress 2.4 with a whitelist of valuesets not to test for but there may be a bug in that section of the code which will be fixed in a future point release.

Generated at Fri Apr 26 11:44:47 EDT 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.