JIRA LINK https://snomed.atlassian.net/browse/IHTSDO-972

IHTSDO Content development – fast track (simple/single changes)

Title

IHTSDO-972

Telehealth monitoring: New intermediate primitive concept

Version Information

Document review

JIRA IHTSDO-972 Telehealth monitoring Documentation Review

Statement of problem as requested or initially identified

The concept |Telehealth monitoring| does not current exist. This concept could not be fully defined, so would be an intermediate primitive.

Relevance to International edition

Monitoring a patient using telehealth is an increasingly common method for monitoring patients that would be relevant in many countries.
Creation of this concept would support:

• Recording of this type of procedure

• Fully defining (or improved logical definition) of other telehealth monitoring concepts e.g. SIRS request 611525 |Telehealth monitoring suspended (situation)|

Related changes impacted by this content development request

This concept represents a specific method of monitoring. Currently there are limited concepts that would be subtypes of this concept.
These concepts are:

• Telehealth asthma monitoring (regime/therapy)

• Telehealth obesity monitoring (regime/therapy)

• Telehealth hypertension monitoring (regime/therapy)

• Telehealth monitoring for chronic disease (regime/therapy)

• Telehealth chronic obstructive pulmonary disease monitoring (regime/therapy)

  • This last concept is a subtype of Telehealth monitoring for chronic disease (regime/therapy) so is not a proximal subtype.

J Case, Head of Terminology has noted the pre-coordination pattern <x> procedure using <y> technique should be used for these types of concepts. This pattern has now been added to the Pre-coordination pattern tracker PCP-207: <Procedure> using <y> technique (procedure)To Do Given the concepts here are current concepts and the work on these for the purposes of this project is limited to making them subtypes of Telehealth monitoring no changes to the descriptions will be made. 

Agreed scope statement

1. Creation of the concept |Telehealth monitoring (regime/therapy)

2. Telehealth monitoring (regime/therapy) would be added as a stated parent of:

   • Telehealth asthma monitoring (regime/therapy)

   • Telehealth obesity monitoring (regime/therapy)

   • Telehealth hypertension monitoring (regime/therapy)

   • Telehealth monitoring for chronic disease (regime/therapy)

Identify additional changes

• The concept |Discussion about telehealth monitoring (procedure)| has the following modelling:

The target value of the |Has focus| relationship would be changed to |Telehealth monitoring| and the concept definition status changed to fully defined.

• The new requested concept |Telehealth monitoring suspended (situation)| will be modelled with |Telehealth monitoring| as the target value for the |Associated procedure| attribute. This will allow the concept to be fully defined. 

 

As part of this work it has been identify that several of the monitoring concepts e.g. |Asthma monitoring| have the potential to be fully defined using the |Has focus| attribute, noting where it is monitoring of a disorder that the disorder would be the target value of the relationship. 

To progress this section of work a small content tracker project has been set up  https://snomed.atlassian.net/browse/IHTSDO-974  to determine/confirm the modelling required for these concepts prior to the changes being made. Comments made by J. Case will be applied to the tracker item.  

It is also worth noting when that work is undertaken work that there is a pre-coordination roadmap pattern issue:  

PCP-195 - artf7888-Monitoring of/for <entity> IN INCEPTION  that has a current status of Temporarily not allowed. This will not impact the current concepts but needs to considered for new content.

Solution proposed
As noted above.

Stakeholder input
Not required. Requested concept |Telehealth monitoring suspended (situation)| will be added outside of this tracker.

Impact assessment
No negative impact is anticipated. As noted above the modelling of some content will be improved.

Risk assessment
Risk of making change: Nil, as subtypes can be identified.
Risk of not making change: Two concepts will need to remain primitive.

Approval process

Priority

?Very high
?High
?Medium
?Low

Specify the basis for the above priority assignment

Supports the modelling a requested concept that is planned for the Jan 17 release.

Content editing
As noted in the agreed scope statement and additional changes sections

Details of content changes
Rules, patterns, guidelines to be followed: Standard editorial guidance only.

Manual quality check
All changes will be checked through the standard internal editing process.

Automated quality check
An additional automated quality check is not indicated. Content will be QA'd through normal processes.

Publish to release branch
January 2017.