2017-09-26 IA Small Group Call

Date

Attendees

Scribe

Goals

  • Continue writing the guidelines for ANF modeling of CDS KNART clinical statements.

Discussion items

TimeItemWhoNotes
5minAgenda Items for TodayKeith and Claude
  • Wants to migrate from the working document that we have, which shows what the components are of a clinical statement, and what are the circumstances.  The document has been getting iteratively better, but we need to wrap up our activity on the ANF.  Part of that is finalizing which fields are broken down into circumstances, particularly for action requests.
  • Claude:  Last week, we discussed UUIDs and we have a proposal to discuss/review.  Keith:  We can do that first and for the document, there are lots of parts that need to be put into a single document.
 25minReview UUID ProposalGroup 
  • Claude:  Order sets and documentation templates are the first types of KNARTs they are working on.
  • Claude:  Having route of administration at the top level of a request is not acceptable.  In the TSR, you would highlight a piece of text, such as "oral," and then there would be a technique for route of administration that gets a UUID.  We can say in the circumstances object there is a list of techniques for which you will get a UUID, and you can give what you think is the right breakdown and we'll see if Terminology agrees.  There would be documentation such as route of administration is different from dosage.  For "150 PO," we'll need to decide if that's 2 UUIDs or 1.
  • Kirsten:  Needs to work through some examples to better understand.  We also need to discuss constraints.  Sarita:  Agreed.  Keith:  The examples can come from the TSRs.
  • Keith:  We must avoid using finding site.  We need consistency and reproducibility across all of these.  We need to have technique separate from topic.  When looking at phenomenon measurement, we'll need to consider if technique should be applied or broken out in the ANF.
  • Keith:  John, how do we define technique and that it should be broken out from a topic?  If we start with words, if you are talking about equipment, it's a technique.  Is there anything in SNOMED?  John:  He doesn't think it exists.  Are you saying for each relevant hierarchy, such as equipment or products, here are the techniques?  That is just an enumeration.  Technique means whatever we want it to mean.  Keith:  Is it reasonable that for technique, we would have a textual description with a few key words and we evolve the guidelines as to what a technique is and have it represented consistently cross the 4 clinical statement types?  Sarita:  On our prior work for routes of administration, one of the issues was overlap in meaning between the route of administration for technique and approach.  She and Kirsten could work on something and have it ready at our next Tuesday call.  Keith:  Regarding the overlap, it's a consequence of not creating a good definition.  He requests that we not try to define technique by retrofitting it into what currently exists in SNOMED but define it and see if we can make a distinction, figure out the overlap, and effectively deal with it.  The definition of technique is "The way you employ a technical skill, method of performance."  It's the "how" you are performing something vs. the "what."
25minANF Modeling Guidelines DocumentGroup
  • Keith:  Thinks we need to transition the document from Kirsten to Claude.  Keith would like to integrate the clinical statement model and show the 4 types of clinical statements.  Claude is the best one to speak to this.  There are also diagrams he has created that need to be included in the document to explain and visualize the data structure.  Kirsten has been focusing on the prose with respect to the details of how we do things, such as what part of the clinical statement represents the topic vs. circumstances.  He believes we are at the strawman of saying this represents version 1 of the fields of circumstance and techniques, perhaps with indication included as part of the list. 
  • Claude:  The circumstances are broader than just the how and includes attribution information at times, such as who was intended to perform a procedure and who requested a procedure.  
  • Keith:  He wants to pull it together so it's a comprehensive document and merge it with Walter's clinical statement white paper, but that's not your concern.  We need to be cognizant that we are calling out, for example, a route of administration but wrap it around the technique field.  We can then focus on what the models are for technique.  By wrapping up ANF, we can then start talking about how CIF relates to it, etc.
  • Kirsten:  From my end, I will keep this latest version and have Claude work on it.  Keith:  Yes, we need to know what the model is in which terminology fits and have ANF 1.0 finished.  Kirsten:  Having put some more examples into the domain-specific table, we need to trace back to the use cases from which they came.  She has done that by footnoting them.  Keith:  After we get ANF 1.0 finished, we can put it into DocBook form and once it's in there, we can directly link it to the use cases.  That is part of the phasing he wants to get done.  He would like to do that by the end of October.
5minOther ItemsGroup
  • Keith:  There is a Glip forum for the IA Small Group, and you can post documents and questions there.  That is where he will see it.
  • Claude:  Several of us have provided examples on how to model the nitroglycerin example that Keith had provided.  Keith:  Let's discuss that on Friday.



Action items

  •