I don't see any changes mentioned in valuesets, but there are a number of revisions beyond just HASH_TOKEN table. Personally, I didn't know there were changes to what I thought was final standard for CDMV5.0 from two months ago Jim
The v5.1 release includes: Three new fields in HASH_TOKEN: TOKEN_03, TOKEN_04, TOKEN_16. Deprecation of 5 fields in HASH_TOKEN: TOKEN_12, TOKEN_17, TOKEN_21, TOKEN_22, TOKEN_23. Updates to the field descriptions in HASH_TOKEN: TOKEN_01, TOKEN_02, TOKEN_05. Corrections to the constraints of PRIVATE_DEMOGRAPHIC. Corrections to the field length and definition of PRIVATE_GEOCODE.GEOCODE_COUNTY. Updates to the Implementation Guidance in PRESCRIBING, HASH_TOKEN, PRIVATE_DEMOGRAPHIC and PRIVATE_ADDRESS_HISTORY. Correction to PRO_SOURCE value set to align with the parseable file for this field. HARVEST table: REFRESH_LDS_ADDRESS_HISTORY_DATE is shortened to REFRESH_LDS_ADDRESS_HX_DATE. Clarified implementation guidance for future dates and PATID consistency. Clarified field implementation guidance for ADDRESS_PERIOD_END in the ADDRESS_HISTORY table. ________________________________ From: Russ Waitman <rwait...@kumc.edu> Sent: Tuesday, October 1, 2019 11:53 AM To: Campbell, James R <campb...@unmc.edu> Cc: GPC STANDARDS <gpc-dev@listserv.kumc.edu> Subject: Re: CDMV5 implementation Non-UNMC email I think the main change is just to align the hashing Russ Waitman On Oct 1, 2019, at 12:24 PM, Campbell, James R <campb...@unmc.edu<mailto:campb...@unmc.edu>> wrote: I assume based upon Datavant presentation that we must be in compliance with CDMV5.1 for our next CDM refresh? Checking the PCORnet desktop, I find the 5.1 documentation but no new valueset documentrs. I assume what they published as CDMV5.0 valuesets are to be employed? Jim The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender. _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu<mailto:Gpc-dev@listserv.kumc.edu> http://listserv.kumc.edu/mailman/listinfo/gpc-dev<https://urldefense.proofpoint.com/v2/url?u=http-3A__listserv.kumc.edu_mailman_listinfo_gpc-2Ddev&d=DwMFAg&c=ZukO2fIan9e5E9v43wuy1w&r=gSA0M7Mz28zWOxVF7u6asW5oh-AQwQaAGLRZagOwI6o&m=BNdOCgYF57PAECIMte7hrDWkvQaIn6tsCwO9CDfSuBg&s=RJASWiyQCUT8_6iX9DpXG9fP8Nhe4hGv0nYQE95jf3g&e=> The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender.
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
