Test code mapping

The first piece of information PKB will use to categorise the data is the specialty code. If this is present (in PV1-10) and you have let us know your code set, then we will be able to apply a meaningful label.

In the absence of a specialty code, each team using PKB can choose how they want the data they generate to be labelled by default. For example, one HIV team may take a multi-disciplinary approach by default, involving all other teams looking after the patient, and thus label their data as "general". Another HIV team may cater to privacy-conscious patients, and thus label their data as "sexual".

Each patient can override the team's default preferences. For example a patient receiving care from an HIV team who label their data as "general" may override the team's choice and apply the "sexual" label instead.

PKB can only apply team- and patient-specific labels if the data point transferred allows us to determine the source team. For the HL7 interface, this requires that the connection is made using team level credentials, or alternatively that a pre-agreed alias is sent in MSH-4 which maps to one of your existing teams.

If the source team is not available, PKB can act on the semantic code (e.g. Snomed, Read). If available in the data, PKB's default privacy rules are applied. For example, CD4 test results of HIV patients are labelled as "sexual" by default.

If no specialty, team, or semantic code is available, the data point is labelled as "general".

The diagram below shows these rules in action.
*patient privacy label overiding in development

Default privacy labels for test results