Just wanted to share experience/ ask if anyone else has managed to have a conversation with anyone at TPP re their 'policy' of mapping/removal of Y-codes when standard Read codes are released.

For example when they issued their swine flu Y-codes in August, the status message claimed they would carry out a 'system wide replacement' when the Read codes are released. Codes were released in October but the Y-codes remain. When I logged the call, the feedback was they have no plans to remove the Y-codes...

I am trying, via CSC/CfH, to find out how we can progress general data quality/good practice discussions with TPP, in particular to find out what their policy is around issuing/managing local codes. Have also spoken to CfH Data Standards who advise there is no documented recommended policy/guidance etc for system suppliers but they will try to follow this up via GPSoC or other channels in terms of good practice.

Just wondered if anyone else had any experience?

Dawn

Hi Dawn

Well as you know i am a sad bugger and when i saw the correct read codes for the swine flu info i changed my templates and searches and did a batch read code replacement. Ran my search the next day and it found nobody. This happened everyday for at least two months before for what ever reason the search eventually found all the patients. Only mildly frustrating. Aon on another point, as for the Health Visitors round here adding the Edinburgh Postalnatal depression score into all new born babies!!! Can't seem to get them to understand that it is an issue for me.

H


[QUOTE=Dawn Friend;4315]Just wanted to share experience/ ask if anyone else has managed to have a conversation with anyone at TPP re their 'policy' of mapping/removal of Y-codes when standard Read codes are released.

For example when they issued their swine flu Y-codes in August, the status message claimed they would carry out a 'system wide replacement' when the Read codes are released. Codes were released in October but the Y-codes remain. When I logged the call, the feedback was they have no plans to remove the Y-codes...

I am trying, via CSC/CfH, to find out how we can progress general data quality/good practice discussions with TPP, in particular to find out what their policy is around issuing/managing local codes. Have also spoken to CfH Data Standards who advise there is no documented recommended policy/guidance etc for system suppliers but they will try to follow this up via GPSoC or other channels in terms of good practice.

Just wondered if anyone else had any experience?

Dawn[/QUOTE]

Dawn
- your work with CSC/CfH, ‘to find out how we can progress general data quality/good practice discussions with TPP, in particular to find out what their policy is around issuing/managing local codes.’ is really appreciated.

I very much wish, like you they would map/remove Y-codes when standard Read codes are released.

I think it would also be very helpful:

- to know that when TPP create a Y….code, it is a temporary measure because a submission for a National code has been submitted and agreed

- if Local (ie Y….. codes in TPP) are included in a clinical system readcode browser that they should be clearly identifiable as such. Practice staff we work with are often unaware of the need to avoid these codes, despite repeated reminders/ resources with this message, because the codes are not that obvious.

Many thanks for what you’re doing, it's very heartening to hear!

Jean


[QUOTE=Haley;4316]Hi Dawn

Well as you know i am a sad bugger and when i saw the correct read codes for the swine flu info i changed my templates and searches and did a batch read code replacement. Ran my search the next day and it found nobody. This happened everyday for at least two months before for what ever reason the search eventually found all the patients. Only mildly frustrating. Aon on another point, as for the Health Visitors round here adding the Edinburgh Postalnatal depression score into all new born babies!!! Can't seem to get them to understand that it is an issue for me.

H[/QUOTE]

Thanks Haley and Jean, glad I am not alone in my frustrations!

Unfortunately I have not made much progress with trying to tackle these issues as yet, but I am still trying....

D