![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
too darn hot
Jul. 24th, 2018 01:57 amIn two words: too hot. (Yes, I realise that the north of England isn't as hit by the current temperatures as the south, and that other parts of the world have it even worse. It's still too hot.)
Writing continues. Though sometimes it feels like a crawl rather than a race. Still trying to work out how I'll resolve the end of the novel.
Work is being less painful than it might be. The air conditioning is working, thank goodness, and we can breathe. (For the moment, at least.) My team - the cross-mappers - finished our current piece of work in the twice-yearly release early. This is generally good, or at least much better than us running late. However, it is a situation which leaves us with (some) time on our hands and a moral obligation to help out the rest of the team, which can result in picking up the annoying jobs that nobody else wants to do. Fortunately, my proactive investigation of useful tasks (ie, looking around for anything to do that wasn't assisting on the helpdesk) coincided with the OPCS-4 development team section needing research doing on a dozen or so new requests, so everyone was happy. (Except perhaps the helpdesk.)
(OPCS-4 is the classification we use to record procedures, such as replacement of hip joint, cauterisation of epistaxis, coronary angioplasty, etc. We update it every couple of years. However, not all update requests are of equal validity - that is, we get a fair number of requests for new codes for things that can already be expressed by existing codes, or that are done about once a year by one hospital in the entire country and probably cannot be considered to be necessary additions to the classification. We therefore have a reasonably strenuous research and peer review process on new requests - which is good, but means work. However, it's often interesting work, and definitely better than answering classification queries on the helpdesk.)
Still too hot. At this rate, Irene's next adventure is going to involve a heatwave, and Kai lounging round in a shirt open to the waist.
Writing continues. Though sometimes it feels like a crawl rather than a race. Still trying to work out how I'll resolve the end of the novel.
Work is being less painful than it might be. The air conditioning is working, thank goodness, and we can breathe. (For the moment, at least.) My team - the cross-mappers - finished our current piece of work in the twice-yearly release early. This is generally good, or at least much better than us running late. However, it is a situation which leaves us with (some) time on our hands and a moral obligation to help out the rest of the team, which can result in picking up the annoying jobs that nobody else wants to do. Fortunately, my proactive investigation of useful tasks (ie, looking around for anything to do that wasn't assisting on the helpdesk) coincided with the OPCS-4 development team section needing research doing on a dozen or so new requests, so everyone was happy. (Except perhaps the helpdesk.)
(OPCS-4 is the classification we use to record procedures, such as replacement of hip joint, cauterisation of epistaxis, coronary angioplasty, etc. We update it every couple of years. However, not all update requests are of equal validity - that is, we get a fair number of requests for new codes for things that can already be expressed by existing codes, or that are done about once a year by one hospital in the entire country and probably cannot be considered to be necessary additions to the classification. We therefore have a reasonably strenuous research and peer review process on new requests - which is good, but means work. However, it's often interesting work, and definitely better than answering classification queries on the helpdesk.)
Still too hot. At this rate, Irene's next adventure is going to involve a heatwave, and Kai lounging round in a shirt open to the waist.
