Clinical Event & Specialty Agreement Results Part II: SSDQA Comparison


dc.contributor.authorWieand, Kaleigh
dc.contributor.otherPEDSnet Data Coordinating Center
dc.date.accessioned2025-12-16T21:51:48Z
dc.date.created2025-09
dc.description- After remapping the hematology specialties that could be re-identified via the source value fields, both Seattle (in the provider domain) and National (in the care site domain) displayed increases in the amount of visits associated with a hematologist. - National, as a result of this remapping, was able to recover all of the patients originally lost in the attrition. - Other than this, the findings from the previous round of specialty analysis stand.
dc.description.abstractThe results of a Clinical Events & Specialty Agreement check using the Multi-Site, Exploratory, Cross-Sectional parameters. This check investigates specialty utilization, both at the provider & care site levels, for patients with a sickle-cell diagnosis. This check was run to evaluate the impact of a targeted remapping of specialties to recover additional information from the source value fields.
dc.identifier.urihttps://hdl.handle.net/20.500.14642/1255
dc.identifier.urihttps://doi.org/10.24373/pdsp-590
dc.publisherPEDSnet
dc.rightsa CC-BY Attribution 4.0 license.
dc.rights.urihttps://creativecommons.org/licenses/by/4.0/
dc.subjectVisit-Level Analysis
dc.subjectCross-Sectional Analysis
dc.subjectMulti-Site Analysis
dc.subjectExploratory Analysis
dc.subject.meshAnemia, Sickle Cell
dc.subject.meshHematologic Diseases
dc.titleClinical Event & Specialty Agreement Results Part II: SSDQA Comparison
dc.typestudy
dspace.entity.typeDQResult
local.admin.notev57
local.description.outcomesThis analysis confirms that remapping these specialties improves patient retention and reflects a more expected pattern of specialty utilization. We formally applied this remapping, by creating an artificial concept identifier to represent hematology specialists that were re-identified, to our CDM and will continue to use this mapping throughout the rest of the analysis.
local.dqcheck.outcomesData Source Adjusted
local.dqcheck.resultobsExpected Output
local.dqcheck.resultobsDisparate Site Behavior
local.subject.DataProvPEDSnet Data Source
relation.isDQCheckOfDQResult8a83d96f-ef0e-4426-a684-45d693c3e962
relation.isDQCheckOfDQResult.latestForDiscovery8a83d96f-ef0e-4426-a684-45d693c3e962
relation.isDQResultOfDQResultc1c970f7-f2f3-45f8-846d-f35091536e2b
relation.isDQResultOfDQResult.latestForDiscoverya54c6e9e-4aa8-462d-9bcb-760a25e0a6a5
relation.isDocumentationOfDQResultc5d447aa-7544-441f-b454-016b43b3bdcd
relation.isDocumentationOfDQResult.latestForDiscoveryc5d447aa-7544-441f-b454-016b43b3bdcd
relation.isOrgUnitOfDQResultbbc643ef-84bd-47d1-b2ae-78b351f3ad42
relation.isOrgUnitOfDQResultda841c56-bb55-405c-8b50-8f221ef62890
relation.isOrgUnitOfDQResult7d0766ee-33d1-4e27-a9a7-db3605a19931
relation.isOrgUnitOfDQResult82e7b586-55bb-4100-91bd-cbff861694ca
relation.isOrgUnitOfDQResult9317d73a-b87c-4f10-8044-2b7eb2d28b34
relation.isOrgUnitOfDQResult30099c48-73a0-4702-b902-90e18dd95b36
relation.isOrgUnitOfDQResult384981f4-38de-42ed-b88c-16ccfd88379d
relation.isOrgUnitOfDQResult405a8c92-423e-4a76-b554-55c63376f603
relation.isOrgUnitOfDQResultff32d2b6-e2f1-443a-b244-befccab19475
relation.isOrgUnitOfDQResult9a70cd88-d272-4a2a-82b2-7b4a1422f809
relation.isOrgUnitOfDQResult.latestForDiscoverybbc643ef-84bd-47d1-b2ae-78b351f3ad42
relation.isStudyOfDQResulta06c92dd-336b-4b1b-b7d9-fb4701104fb1
relation.isStudyOfDQResult.latestForDiscoverya06c92dd-336b-4b1b-b7d9-fb4701104fb1

Files

Original bundle

Now showing 1 - 2 of 2
Loading...
Thumbnail Image
Name:
cnc_sp_ms_exp_cs_caresite_dqr4.csv
Size:
37.54 KB
Format:
Comma-Separated Values
Loading...
Thumbnail Image
Name:
cnc_sp_ms_exp_cs_provider_dqr4.csv
Size:
53.8 KB
Format:
Comma-Separated Values

Domains