Difference between revisions of "PCD Technical Committee Action Items"

From IHE Wiki
Jump to: navigation, search
m (new content from 7-15 page)
(Items 200 - 209)
 
(582 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 +
See also [[PCD Technical Committee Closed Action Items]] page.
 +
 +
To see changes between current and last(or any earlier) versions of the action item list, click the history tab at the top of the page, select versions to compare and click compare command.
 +
 +
Significant recent changes, other than dates, will be in bold.
 +
 +
==Items 60 - 69 Are Closed ==
 +
 +
==Items 70-79 Are Closed==
 +
 +
==Items 80-89 are closed==
 +
 +
==Items 90-99 are closed==
 +
 +
==Items 100-109 are closed==
 +
 +
==Items 110-119 are closed==
 +
 +
==Items 120-129 are Closed==
 +
 +
:{|border="2"
 +
|-
 +
 +
 +
|}
 +
 +
==Items 130-139 are closed==
 +
 +
==Items 140-149  are Closed==
 +
 +
==Items 150-159 are Closed==
 +
 +
==Items 160-169 are Closed==
 +
 +
==Items 170-179 are Cosed==
 +
 +
==Items 180-189 are closed==
 +
 +
==Items 190-199==
 +
 +
:{|border="2"
 +
|-
 +
! width="5%"  align="center" |No.
 +
! width="15%"  align="left"  |Action Item
 +
! width="5%"  align="left"  |Owner
 +
! width="5%  align="left"  |Participants
 +
! width="10%  align="left"  |Due
 +
! width="5%  align="left"  |Open/Closed
 +
!              align="left"  |Description/Update
 +
 +
 +
 +
 +
|-
 +
| align="center" | 196
 +
| '''<Action Item>''' | Add PCD specific values to HL7 table 78
 +
| '''<Owner>:'''  | John Garguilo
 +
| '''<Participants>''' |
 +
| '''<Due Date>'''  | July 7, 2021
 +
| '''<Status>''' |OPEN
 +
| '''<Comments>:'''  | From 2016 NA Connectathon.  Status is in PCD TF v5 Vol2 page 119 at line 2890, but not in NIST Tool which only supports values from HL7 Table 0078.  We can suggest table changes to HL7, John will take this to HL7.
 +
April 21, 2016:  Values are in TF.  John will approach HL7 vocab group at their meeting in two weeks.  Anticipates no issue.  If not successful, will add XML table.  Set to PC&TC meeting May 18.
 +
:  May 18, 2016:  Couldn't find the term we wanted to add, please send it to John.  Change date to June 1.  Should be in Vol 2, reference to table 78.  Set to next TC meeting.
 +
:June 1, 2016:  Change to July 6 TC call.
 +
: July 6, 2016: Nothing new, set to next TC meeting.
 +
: Aug 3, 2016:  Nothing new, set to next TC meeting.
 +
: Sep 7, 2016:  Will try to present at HL7, set to Oct PC/TC meeting.  Set to Oct meeting.
 +
:Oct 5, 2016:  Contacted Vocabulary working group, almost done.  Will extend tables with appropriate codes.  A simple add to get the changes put in. Set to F2F.
 +
: Oct 12, 2016: Add PCD specific values to HL7 table 78 – pp61 discusses it, we have values not in HL7.    HL7:  write up proposal for them to approve or not.  These are generic enough for other to use them, it is also a way to get some null values in there.  Can we create a local table to address it – Yes.  We will need to do that for the Connectathon.  But was only checked against HL7 table for DEC; need to add a local DEC table.  May want to define a write operation as well.  Targeting HL7 Jan 2017 to have values added to Table 3.9.4.1.2.5-3.  Set due date to Feb TC meeting.
 +
:Feb 1, 2017: Will submit to HL7 vocabulary group.  Will present to May HL7 meeting.  Review May 17th PC and TC.
 +
:May 17, 2017:  Needs some paperwork done and sent, should be done in a month.  Review June 21.
 +
:July 12, 2017:  Nothing new.  Review at Aug TC.
 +
:Aug 15, 2017:  No new information, move to Sep meeting.
 +
:Sep 27, 2017:  No update, effort to get these formally into HL7.  John will contact Ted Klein at HL7, set to Oct TC.
 +
:Oct 5 2017:  Validated and put in tool.  Contacted Ted Klein, moving forward.  Should be completed Nov 29.  Set to Dec TC.
 +
:Dec 20 2017:  John not available, move to Jan TC meeting.
 +
:Jan 3, 2018: No update, move to Feb TC.
 +
:Feb 7, 2018:  John still needs to submit something.  Set to March TC meeting.
 +
:Mar 21, 2018:  No update, move to Apr F2F.
 +
:April 12, 2018:  John not available, move to April PC&TC.
 +
:April 19, 2018:  No update, move to May TC meeting.
 +
: May 2, 2018:  Work continues, hope to make progress from HL7 meetings.  Set to June TC meeting.
 +
: June 13, 2018:  No new info, move the joint PC&TC meeting.
 +
: June 27, 2018:  John G not available, set to next TC meeting.
 +
: July 25, 2018:  No update yet, set to Sept TC meeting.
 +
: Aug 15, 2018:  John submitted info to Ted Klein, will need to follow up at HL7 meeting.  He can update at F2F.
 +
: Oct 18, 2018: John not available, move to next TC meeting.
 +
: Nov 5, 2018:  No new info, next HL& should provide update.  Set to Jan meeting.
 +
: Jan 2, 2019:  NIST unavailable, set to Feb meeting
 +
: Feb 6, 2019: John not here, move to Joint PC/TC
 +
: Mar 6, 2019: John not available, move to F2F
 +
: Apr 25, 2019: John will get it in as soon as he can. Review in June
 +
: June 5, 2019: John not on call, set to July meeting
 +
: July 10, 2019:  No change, move to August
 +
: Aug 7, 2019: Checks data validity. John not available, move to next month.
 +
: Sep 4, 2019: No update, move to next month.
 +
: Nov 6, 2019:  No update, move to Dec.
 +
: Dec 4, 2019: Review after next HL7 meeting. Move to March.
 +
: March 4, 2020:  John not available, move to April meetings
 +
: April 1, 2020:  May HL7 cancelled, unable to do anything for now, move to September meeting.
 +
: Sept 2, 2020: HL7 meeting this month, move to F2F
 +
: Oct 8, 2020: No update.  Move to February.
 +
: Feb 3, 2021: John not available, move to next meeting.
 +
: Mar 10, 2021:  Nothing new, need to talk to Ted Cline.  Review after HL7 meetings, set to June.
 +
: April 29, 2021:  Found a new way to work on this.  They have weekly meetings, so will try to get it on their agenda.  Hope to make progress by HL7 meeting week last of May.  Review June 2.
 +
: '''June 2, 2021:  John not available, review July meeting.'''
 +
 +
 +
 +
|}
 +
 +
==Items 200 - 209==
 +
  
 
:{|border="2"  
 
:{|border="2"  
Line 11: Line 124:
  
 
|-
 
|-
| align="center" | 60
+
| align="center" | 200
| '''<Action Item>''' |Update TF
+
| '''<Action Item>''' | MDS, Containment and VMD Requirements
| '''<Owner>:'''  |Todd, Ken
+
| '''<Owners>:'''  | Paul Schluter
| '''<Participants>''' | John Rhoads
+
| '''<Participants>''' |  
| '''<Due Date>'''  | 2009.07.01
+
| '''<Due Date>'''  | Aug 4, 2021
| '''<Status>''' |OPEN
+
| '''<Status>''' | Open
| '''<Comments>:'''  | Meetings have begun. The update will include PIB, SPD. Then it will be released for public comment (September). Todd asked for comments, suggestions. Ken has cleaned up Volume 1 in preparation for updating it.  
+
| '''<Comments>:'''  | June 27, 2018:  Created. Need to make consistent, so they can be applied uniformly by NIST tool. Set to next TC meeting
Todd will ask the IHE Cochairs if the format must be changed to the new format or can be left as is. A Google Group has been established. Distribute the updated TF for use in this cycle’s implementation for the Connectathon. John Rhoads will prepare the CP for the TF. TC to set the date for the TF public comment release. John Rhoads suggested members review and comment on the TF. He suggested emailing Todd with copies to Ken and himself. A format change to the TF is anticipated. This would place the boiler plate into volume 0. '''CPs will continue to be received as we go forward to the Connectathon. A number have been received. Paul noted that coordination with Continua will result in additional items. Todd requested that CPs be submitted now as the TF is reviewed. CPs addressing a WG profile will first be reviewed by the WG and then be brought to the TC.'''
+
: July 25, 2018: No update yet, move to F2F TC meeting.
 +
: Oct 18, 2018: Loose, not tested by NIST tools. Required disclosure at CMI. Need to assemble ‘uber’ models. How rigorous. Part may include retrofitting specificity in TF. May need general x-type path. May be able to use a tool like FHIR’s to create the containment models. Also want to clearly state what containment is. Discussed options and current process with some examples. Need to work out wrinkles for multiple devices doing the same thing. Need to solve persistence issue. Example: BP monitoring channels, when expanding channels, need to ensure the original maintains its channel number. Discussed different IV pump models as well as monitoring. Found a challenge with ACM; Alarms and other messages. If the alarm is in the first message, then another message is generated with another field completed, the alarm may not be at the same location in the message. Oliver will draft a White Paper to address MDS, persistence and channel identification, what works, doesn’t work and mine fields. He has a lot of notes already. Will review Dec TC meeting.
 +
:Dec 19, 2018 - Using it, NIST working on it.  Until 10101r is out the door, won’t be able to focus on it. Not sure next stage of ‘done’ is.  Push out to February, and discuss at DPI meetings.
 +
: Feb 6, 2019: Nothing right now, move to next TC.
 +
: Mar 6, 2019: Should be able to start on it again soon. Review next PC&TC
 +
: Mar 20, 2019:  No new info, could use a ½ hour discussion at F2F.  Set to F2F
 +
: Apr 25, 2019Related to the OBX-4 question, need to figure out what to do. It is a ‘should’, do we make it a ‘shall’? If so, we need to let implementer know well before Connectathon. Include Lexicographic order. Move out to June meeting.
 +
: June 5, 2019: Tabled for now, move to July
 +
: July, 10, 2019: Paul not here, fair amount of discussion recently.  Michael Faughn working on RTMMS, which will help. Also need to work on TF and IGAMPT.  Move to August
 +
:-Aug 7, 2019: Will work on it after Events and Alerts.  Michael and Nicholas will work on it when they have time. Move to September.
 +
: Sep 4, 2019: Should be able to convene a call and take care of it.  Move to October
 +
: Nov 6, 2019:  Some progress, move to Dec.
 +
: Dec 4, 2019: No new info, move to Feb.
 +
: Feb 5, 2020: Making progress, move to F2F.
 +
: Apr 23, 2020 - Containment modeling important, can resolve problems, especially during Connectathon.  Asking those that need terms to create containment models.  This limits the need for inspecting messages by hand, as computers are much better at it. He, Michael, and Brian are working on consistent output data as well.  NIST is working with CDC on a similar issues regarding COVID-19 tracking.  Inconsistent data quality is an issue for them as well.  John G – Nicholas will have some info that will help later during F2F.  Move to next F2F.
 +
: Oct 8, 2020 - Should be resolved with Pump group and work with Michael Faughn.  Move out to January call.
 +
: Jan 6, 2021 - Will wrap up when Michael Faughn can focus on it.  Review next month.
 +
: Feb 3, 2021 - Still working on it - Michael Faughn still working on another project.  Move to March.  Add 'Containment' to title.
 +
: Mar 10, 2021:  Michael Faughn still porting Rosetta.  Paul wrote a containment model.  Pathway figured out, should be able to move forward and use with other devices.  Review in May.
 +
: '''April 29, 2021:  Coupled with Michael Faughn's availability.  Been capturing terms at various workgroup meetings.  Set to August meeting.'''
  
|-
 
| align="center" | 62
 
| '''<Action Item>''' |Incorporate Bar Coding into ADT implementations; which domain is responsible?
 
| '''<Owner>:'''  |Todd
 
| '''<Participants>''' | Co-chairs
 
| '''<Due Date>'''  | 2009.07.01
 
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  | Please see summary of June 3 for history http://wiki.ihe.net/index.php?title=PCD_TC_2009-06-03_Webex#Discussion. John Rhoads reviewed the topic as discussed at the DCC. Ken and Todd took this to the DCC approximately 6 months ago. The DCC suggested PCD take the lead and coordinate the various IHE Domain. John indicated this was the same approach the DCC took again recently. Todd noted that Khalid is developing an approach for DPI and asked that John take this back to the DCC and he agreed to do so. Paul asked if bar codes (which are available in different standards) are the only identifier of interest. Others could include the patient’s photo. Todd suggested the PC draft a brief profile proposal that could be used to recruit ITI, Radiology and possibly PCC to join the effort. John asked Khalid if he would lead this effort and Khalid agreed to give this some thought. Paul noted that PCD-01 permits multiple patient identifiers. Change date to July 1.
 
  
 
|-
 
|-
| align="center" | 66
+
| align="center" | 202
| '''<Action Item>''' | Prepare profiles for registration.
+
| '''<Action Item>''' | MEMDMC CP to make PID and PV1 segments optional
| '''<Owner>:'''  | John Garguilo
+
| '''<Owner>:'''  | Monroe Pattillo
| '''<Participants>''' | Al Engelbert, Todd Cooper, Robert Flanders.
+
| '''<Participants>''' | Dalibor, John Rhoads
| '''<Due Date>'''  | 2009.07.15
+
| '''<Due Date>'''  | July 7, 2021
| '''<Status>''' |OPEN
+
| '''<Status>''' | Open
| '''<Comments>:'''  | PCD likely won’t finalize the application until the TF has been updated and following the public comment period. Todd set up Google Group and Wiki Page to establish a baseline. The PCD will work with NIST for validation. John Garguilo believes two of the three profiles are now complete and correct in the MWB. It is anticipated that the other PCD transactions shall be registered after PCD-01 is complete. John Garguilo has requested that companies post their profiles at: [ftp://ftp.ihe.net/Patient_Care_Devices/Connectathons/Yr3-2009/Yr3-PreConnectathonTesting/ PCD Year 3 Pre-Connectathon Testing FTP Site]. John Rhoads requested that this be addressed early in the cycle. Manny to request members post sample messages for past and future work and note any issues that need to be fixed. NIST is developing test scenarios, requiring the profile and constraints. The PIV WG is the initial profile. John reminded the group that MWB files are needed and should be posted to the ftp site.  
+
| '''<Comments>:'''  | Apr 25, 2019: MEMDMC profile to change via CP to use a message template of ORU_R(as allocated by O&O) which affords it the ability to make the usage of the PID and PV1 segments as optional for MEMDMC use cases. If PID and/or PV1 segments are present they should be populated per the IHE PCD TF.  We did this with ACM, so should be able to do so in MEM.
 +
: May 1, 2019: Getting a new trigger event from HL7. We can start testing to this. Won’t make official until HL7 releases new normative.  Will need to talk to NIST about flagging this in testing. Set to June TC.
 +
: June 5, 2019: Dalibor not here, move to July meeting.
 +
: July 10, 2019:  Nothing new, move to August.
 +
: Aug 7, 2019: HL7 change, NIST tool isn't clear on how to communicate needed info. Add John Rhoads to Participant list.
 +
: Sep 4, 2019:  Up to HL7 meeting to communicate MEMDMC msg.  Conflict in use of PID segment. MEMDMC needs it’s own trigger.  Monroe will send to John G for the agenda.  Move to October.
 +
: Nov 6, 2019:  At HL7 O&O.  They have a huge backlog, will take time.  Problem with HL7 standard, a bit of an unstable reference loop.  Is it possible to ‘pre-adopt’ the triggers?  Yes, if HL7 says they will create them. Move to Dec.
 +
: Dec 4, 2019: Still waiting on HL7.  Review in March.
 +
: March 4, 2020: Waiting for HL7.  In the queue, not discussed yet. Needs a promoter on the committee at HL7 O&O to ensure it’s addressed.  John Rhoads will disuss with a member.  Move to F2F.
 +
: Apr 23, 2020 - Once triggers are officially committed by HL7, they can implement it.  Monroe isn’t sure should be actually owner of this.  John Rhoads talks to O&O a lot. They have a lot to do with limited resources.  He will take ownership.  Move to next F2F.
 +
: Oct 8, 2020: In HL7 queue, move to February, after HL7 meeting.
 +
: Feb 3, 2021 - Need new MEM trigger to avoid PHI info.  Move to spring F2F.
 +
: April 29, 2021:  Passed it into HL7 Orders and Observations, out of their hands now.  Has Monroe contacted Hans?  John will send his contact to Monroe.  Set to June meeting.
 +
: '''June 2, 2021: Monroe sent email to liaison, not reply yet.  Move to July.'''
  
 
|-
 
|-
| align="center" | 77
+
| align="center" | 206
| '''<Action Item>''' | Preparing a Proposal to HL7 for Pharmacy WG (new name)
+
| '''<Action Item>''' |  
| '''<Owner>:'''  | Gary Meyer
+
| '''<Owner>:'''  |  
| '''<Participants>''' | Jeff Rinda, Al Engelbert 
+
| '''<Participants>''' |  
| '''<Due Date>'''  | 2009.07.01
+
| '''<Due Date>'''  |  
| '''<Status>''' |OPEN
+
| '''<Status>''' |  
| '''<Comments>:'''  | Jeff noted this is not a critical issue, but the pharmacy group needs to address the issue. '''Gary is monitoring the Pharmacy WG. They are focused on community practice. Gary suggested that about a third of this work will be useful for institutional practice. Ruth noted that HITSP is working on the ordering process. NCPCP is working on an HL7 2.5 messaging process. This work is US focused and may become an issue internationally. ''' They may not be interested in addressing this in this cycle (Atlanta the week of Sept. 21).
+
| '''<Comments>:'''  |  
 +
 
  
 
|-
 
|-
| align="center" | 79
+
| align="center" | 207
| '''<Action Item>''' | Change Proposal Tutorial
+
| '''<Action Item>''' |  
 
| '''<Owner>:'''  |  
 
| '''<Owner>:'''  |  
 
| '''<Participants>''' |  
 
| '''<Participants>''' |  
| '''<Due Date>'''  | 2009.07.01
+
| '''<Due Date>'''  |  
| '''<Status>''' |OPEN
+
| '''<Status>''' |  
| '''<Comments>:'''  | Provide a tutorial on filing Change Proposals. These have been suggested and need CPs: ACM: clarify coding of multiple aspects of an alarm; Infusion Pump: clarify coding. John Rhoads / Todd Cooper to contact those developing CPs to ensure the process is understood and properly managed.
+
| '''<Comments>:'''  |
|-
+
| align="center" | 82
+
| '''<Action Item>''' | OID for PCD
+
| '''<Owner>:'''  | Todd, John Rhoads
+
| '''<Participants>''' | 
+
| '''<Due Date>'''  | 2009.07.01
+
| '''<Status>''' |OPEN
+
| '''<Comments>:'''  | Manny to follow up on obtaining and OID.  Todd put up a Wiki page to describe managing the OID. John Rhoads will flesh that out. Change date to next meeting. '''John will report on current OID management discussions within the IHE DCC and update the IHE PCD OID page accordingly. The IHE Domain Coordination Committee has had a very active discussion re. the management of OIDs within IHE. This is very positive re. having a coordinated mangagement process and method (e.g., repository) in the near future.
+
'''
+
  
 
|-
 
|-
| align="center" | 83
+
| align="center" | 208
| '''<Action Item>''' | MOUs
+
| '''<Action Item>''' |  
| '''<Owner>:'''  | Sandy
+
| '''<Owner>:'''  |  
 
| '''<Participants>''' |  
 
| '''<Participants>''' |  
| '''<Due Date>'''  | 2009.07.01
+
| '''<Due Date>'''  |  
| '''<Status>''' |OPEN
+
| '''<Status>''' |  
| '''<Comments>:'''  | Follow up MOU status with CIMIT, ASTM. It is on the ASTM executive meeting agenda next week. Ken reported that Julian presented this to the ASTM. The outcome has not been reported. '''Ken will follow-up with Julian Goldman to determine the current status.'''
+
| '''<Comments>:'''  |
 +
 
  
 
|-
 
|-
| align="center" | 84
+
| align="center" | 209
| '''<Action Item>''' | Patient Identity and PCD Messages
+
| '''<Action Item>''' |  
| '''<Owner>:'''  | Todd, Khalid, Gary
+
| '''<Owner>:'''  |  
 
| '''<Participants>''' |  
 
| '''<Participants>''' |  
| '''<Due Date>'''  | 2009.07.01
+
| '''<Due Date>'''  |  
| '''<Status>''' |OPEN
+
| '''<Status>''' |  
| '''<Comments>:'''  | How best to accomplish this tie will be addressed in the white paper for further development as a supplement to PIB (Todd). Coordination with IEEE (-20103 CCOM) and ICE-PAC will be accomplished Jan. Draft a patient association brief profile proposal (Khalid). The A04 registration message is not the commonly used message, while A01 is used by hospitals at admission (Gary). Gary will review this issue and it will be factored into the CPs for publication and testing in the 2010 Connectathon. Also see 62. '''Note related discussions in the Infusion Pump WG.'''
+
| '''<Comments>:'''  |
  
 +
 +
|}
 +
 +
==Tracking Related Items, 1-20 ==
 +
 +
:{|border="2"
 
|-
 
|-
| align="center" | 86
+
! width="5%"  align="center" |Number
| '''<Action Item>''' | Test Tools
+
! width="50%"  align="left"  |Item and Relationships
| '''<Owner>:'''  | John Garguilo, Rob Snellick
+
! width="5%  align="left"  |Date Added to List
| '''<Participants>''' | Manny
+
! width="5%  align="left"  |Date Closed
| '''<Due Date>'''  | 2009.07.15
+
!              align="left"   |Description/Update
| '''<Status>''' |OPEN
+
| '''<Comments>:'''  | NIST will explore a registry for MWB files (Rob). Manny to request PCD Connectathon WG to post MWB files. Change date to June 17, add John Garguilo to the effort. '''NIST is open to providing incremental releases of "test artifacts" (which include MWB profiles).  Need to determine when such information is desired to be available for viewing/browsing.  This information would be part of the Testing Infrastructure as part of a public repository. Can we establish a date to make this available by? Members were asked to send Garguilo any MWB files that should be considered when developing registered profiles. '''
+
  
 
|-
 
|-
| align="center" | 87
+
| align="center" | 1
| '''<Action Item>''' | IDCO
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  | Nick
+
VA proposal on PulseOx - write up details / issues to TC (Ioana S./Greg S.). Provide mappings to x73 of what VA has from LOINC & SNOMED CT - VA to encode (encode all information?)
| '''<Participants>''' |
+
| '''<Date Added>:'''  | F2F Oct. 2011
| '''<Due Date>'''  | 2009.07.01
+
| '''<Date Closed>''' |  
| '''<Status>''' |OPEN
+
| '''<Description/Update>'''  |  
| '''<Comments>:'''  | Is there another transaction for pushing an IDCO report? ICDO is looking for alternatives. Supplement is out for public comment until July 1.  
+
   
 
|-
 
|-
| align="center" | 88
+
| align="center" | 2
| '''<Action Item>''' | Cycle 4 Supplement Status
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  | Ken, Todd
+
DCM (Detailed Clinical Model for Devices) - Develop/provide a publication in a form that will be given to IHE-PCD (Ioana S.) due
| '''<Participants>''' |
+
| '''<Date Added>:'''  | F2F Oct. 2011
| '''<Due Date>'''  | 2009.07.01
+
| '''<Date Closed>''' | Oct 5, 2017
| '''<Status>''' |OPEN
+
| '''<Description/Update>'''   | Oct 5, 2017: Reviewed at F2F. Unanimous decision by TC to sunset this item.
| '''<Comments>:''' | John Rhoads, Monroe, Paul offered to review the WCM document. Cycle 4 Supplement Status - Anticipated release dates are: IDCO - June 1; PIV - June 1; RTM - June 1; WCM - September 1. White Papers: DPI and MEM will be available this summer. PIV: Recent WG F2F: Todd briefly summarized the meeting. Those interested are referred to the Wiki page (see agenda list above). He noted it was a very productive meeting. RTM update: Paul found 40 errors and as a result is looking at automating the process for identifying them. He noted the harmonized table is looking good. Work continues on RTM ventilator terms. The RTM update should be available for TC ballot in about 10 days.  
+
  
CPs: A number of change proposals are in development. He suggested that the PIV WG review these as soon as possible.
+
|-
 +
| align="center" | 3
 +
| '''<Item and Relationships>''' | SFT Segment - Desire to include info from pumps, software segment preferred.
 +
| '''<Date Added>:'''  | F2F April 12, 2018
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
  
 
|-
 
|-
| align="center" | 89
+
| align="center" | 4
| '''<Action Item>''' | Verify process for “public comment” period
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  | Todd, John Rhoads
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' | 2009.07.15
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
+
| '''<Comments>:'''  | '''Verify process for “public comment” period, esp. for CPs; verify it is properly and appropriately applied to the RTM updates; publish to TC (esp. CP editors Jeff Rinda & Rugh Berge). Also in Item 60: CPs will continue to be received as we go forward to the Connectathon. A number have been received. Paul noted that coordination with Continua will result in additional items. Todd requested that CPs be submitted now as the TF is reviewed. CPs addressing a WG profile will first be reviewed by the WG and then be brought to the TC. John Rhoads has reviewed the ITI procedure and provided a modified version for the PCD. Substantial discussion followed and John will update the diagram. Paul asked if there is an appeal process to resolve conflicts. Todd will research the appeal process.
+
'''
+
  
 
|-
 
|-
| align="center" | 90
+
| align="center" | 5
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' | 2009.07.01
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
+
| '''<Comments>:'''  |  
+
  
 
|-
 
|-
| align="center" | 91
+
| align="center" | 6
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |  
+
| '''<Date Closed>''' |
| '''<Due Date>'''  | 2009.07.01
+
| '''<Description/Update>'''  |
| '''<Status>''' |OPEN
+
 
| '''<Comments>:'''  |  
+
|-
 +
| align="center" | 7
 +
| '''<Item and Relationships>''' |  
 +
| '''<Date Added>:'''  |  
 +
| '''<Date Closed>''' |  
 +
| '''<Description/Update>'''  |
 +
 
 +
|-
 +
| align="center" | 8
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |  
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
 
 +
|-
 +
| align="center" | 9
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
 
 +
|-
 +
| align="center" | 10
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
 
 +
|-
 +
| align="center" | 11
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 12
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
|-
 +
| align="center" | 13
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
|-
 +
| align="center" | 14
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
|-
 +
| align="center" | 15
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
|-
 +
| align="center" | 16
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
|-
 +
| align="center" | 17
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
|-
 +
| align="center" | 18
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
 
 +
|-
 +
| align="center" | 19
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
 +
 
 +
|-
 +
| align="center" | 20
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 
  
  
 
|}
 
|}
  
 +
==Tracking Related Items, 21-40 ==
 +
 +
:{|border="2"
 +
|-
 +
! width="5%"  align="center" |Number
 +
! width="50%"  align="left"  |Item and Relationships
 +
! width="5%  align="left"  |Date Added to List
 +
! width="5%  align="left"  |Date Closed
 +
!              align="left"  |Description/Update
 +
 +
|-
 +
| align="center" | 21
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 22
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 23
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 24
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 25
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 26
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 27
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 28
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
 +
|-
 +
| align="center" | 29
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
 +
|-
 +
| align="center" | 30
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
 +
 +
|}
  
Return to [[Patient Care Device]] home
+
See also [[PCD Technical Committee Closed Action Items]] page.
  
 +
=='''Links to PCD TC Meetings'''==
 +
Go to most recent/past meetings or next meeting [[:Category: PCD Meeting]]
  
 +
[[Patient Care Device]] home
  
 
[[Category:PCD]]
 
[[Category:PCD]]
 +
[[Category:PCD Reference Pages]]

Latest revision as of 10:28, 2 June 2021

See also PCD Technical Committee Closed Action Items page.

To see changes between current and last(or any earlier) versions of the action item list, click the history tab at the top of the page, select versions to compare and click compare command.

Significant recent changes, other than dates, will be in bold.

Items 60 - 69 Are Closed

Items 70-79 Are Closed

Items 80-89 are closed

Items 90-99 are closed

Items 100-109 are closed

Items 110-119 are closed

Items 120-129 are Closed

Items 130-139 are closed

Items 140-149 are Closed

Items 150-159 are Closed

Items 160-169 are Closed

Items 170-179 are Cosed

Items 180-189 are closed

Items 190-199

No. Action Item Owner Participants Due Open/Closed Description/Update



196 Add PCD specific values to HL7 table 78 John Garguilo July 7, 2021 OPEN From 2016 NA Connectathon. Status is in PCD TF v5 Vol2 page 119 at line 2890, but not in NIST Tool which only supports values from HL7 Table 0078. We can suggest table changes to HL7, John will take this to HL7.

April 21, 2016: Values are in TF. John will approach HL7 vocab group at their meeting in two weeks. Anticipates no issue. If not successful, will add XML table. Set to PC&TC meeting May 18.

May 18, 2016: Couldn't find the term we wanted to add, please send it to John. Change date to June 1. Should be in Vol 2, reference to table 78. Set to next TC meeting.
June 1, 2016: Change to July 6 TC call.
July 6, 2016: Nothing new, set to next TC meeting.
Aug 3, 2016: Nothing new, set to next TC meeting.
Sep 7, 2016: Will try to present at HL7, set to Oct PC/TC meeting. Set to Oct meeting.
Oct 5, 2016: Contacted Vocabulary working group, almost done. Will extend tables with appropriate codes. A simple add to get the changes put in. Set to F2F.
Oct 12, 2016: Add PCD specific values to HL7 table 78 – pp61 discusses it, we have values not in HL7. HL7: write up proposal for them to approve or not. These are generic enough for other to use them, it is also a way to get some null values in there. Can we create a local table to address it – Yes. We will need to do that for the Connectathon. But was only checked against HL7 table for DEC; need to add a local DEC table. May want to define a write operation as well. Targeting HL7 Jan 2017 to have values added to Table 3.9.4.1.2.5-3. Set due date to Feb TC meeting.
Feb 1, 2017: Will submit to HL7 vocabulary group. Will present to May HL7 meeting. Review May 17th PC and TC.
May 17, 2017: Needs some paperwork done and sent, should be done in a month. Review June 21.
July 12, 2017: Nothing new. Review at Aug TC.
Aug 15, 2017: No new information, move to Sep meeting.
Sep 27, 2017: No update, effort to get these formally into HL7. John will contact Ted Klein at HL7, set to Oct TC.
Oct 5 2017: Validated and put in tool. Contacted Ted Klein, moving forward. Should be completed Nov 29. Set to Dec TC.
Dec 20 2017: John not available, move to Jan TC meeting.
Jan 3, 2018: No update, move to Feb TC.
Feb 7, 2018: John still needs to submit something. Set to March TC meeting.
Mar 21, 2018: No update, move to Apr F2F.
April 12, 2018: John not available, move to April PC&TC.
April 19, 2018: No update, move to May TC meeting.
May 2, 2018: Work continues, hope to make progress from HL7 meetings. Set to June TC meeting.
June 13, 2018: No new info, move the joint PC&TC meeting.
June 27, 2018: John G not available, set to next TC meeting.
July 25, 2018: No update yet, set to Sept TC meeting.
Aug 15, 2018: John submitted info to Ted Klein, will need to follow up at HL7 meeting. He can update at F2F.
Oct 18, 2018: John not available, move to next TC meeting.
Nov 5, 2018: No new info, next HL& should provide update. Set to Jan meeting.
Jan 2, 2019: NIST unavailable, set to Feb meeting
Feb 6, 2019: John not here, move to Joint PC/TC
Mar 6, 2019: John not available, move to F2F
Apr 25, 2019: John will get it in as soon as he can. Review in June
June 5, 2019: John not on call, set to July meeting
July 10, 2019: No change, move to August
Aug 7, 2019: Checks data validity. John not available, move to next month.
Sep 4, 2019: No update, move to next month.
Nov 6, 2019: No update, move to Dec.
Dec 4, 2019: Review after next HL7 meeting. Move to March.
March 4, 2020: John not available, move to April meetings
April 1, 2020: May HL7 cancelled, unable to do anything for now, move to September meeting.
Sept 2, 2020: HL7 meeting this month, move to F2F
Oct 8, 2020: No update. Move to February.
Feb 3, 2021: John not available, move to next meeting.
Mar 10, 2021: Nothing new, need to talk to Ted Cline. Review after HL7 meetings, set to June.
April 29, 2021: Found a new way to work on this. They have weekly meetings, so will try to get it on their agenda. Hope to make progress by HL7 meeting week last of May. Review June 2.
June 2, 2021: John not available, review July meeting.


Items 200 - 209

Number Action Owner Participants Due Date Status Comments
200 MDS, Containment and VMD Requirements Paul Schluter Aug 4, 2021 Open June 27, 2018: Created. Need to make consistent, so they can be applied uniformly by NIST tool. Set to next TC meeting
July 25, 2018: No update yet, move to F2F TC meeting.
Oct 18, 2018: Loose, not tested by NIST tools. Required disclosure at CMI. Need to assemble ‘uber’ models. How rigorous. Part may include retrofitting specificity in TF. May need general x-type path. May be able to use a tool like FHIR’s to create the containment models. Also want to clearly state what containment is. Discussed options and current process with some examples. Need to work out wrinkles for multiple devices doing the same thing. Need to solve persistence issue. Example: BP monitoring channels, when expanding channels, need to ensure the original maintains its channel number. Discussed different IV pump models as well as monitoring. Found a challenge with ACM; Alarms and other messages. If the alarm is in the first message, then another message is generated with another field completed, the alarm may not be at the same location in the message. Oliver will draft a White Paper to address MDS, persistence and channel identification, what works, doesn’t work and mine fields. He has a lot of notes already. Will review Dec TC meeting.
Dec 19, 2018 - Using it, NIST working on it. Until 10101r is out the door, won’t be able to focus on it. Not sure next stage of ‘done’ is. Push out to February, and discuss at DPI meetings.
Feb 6, 2019: Nothing right now, move to next TC.
Mar 6, 2019: Should be able to start on it again soon. Review next PC&TC
Mar 20, 2019: No new info, could use a ½ hour discussion at F2F. Set to F2F
Apr 25, 2019Related to the OBX-4 question, need to figure out what to do. It is a ‘should’, do we make it a ‘shall’? If so, we need to let implementer know well before Connectathon. Include Lexicographic order. Move out to June meeting.
June 5, 2019: Tabled for now, move to July
July, 10, 2019: Paul not here, fair amount of discussion recently. Michael Faughn working on RTMMS, which will help. Also need to work on TF and IGAMPT. Move to August
-Aug 7, 2019: Will work on it after Events and Alerts. Michael and Nicholas will work on it when they have time. Move to September.
Sep 4, 2019: Should be able to convene a call and take care of it. Move to October
Nov 6, 2019: Some progress, move to Dec.
Dec 4, 2019: No new info, move to Feb.
Feb 5, 2020: Making progress, move to F2F.
Apr 23, 2020 - Containment modeling important, can resolve problems, especially during Connectathon. Asking those that need terms to create containment models. This limits the need for inspecting messages by hand, as computers are much better at it. He, Michael, and Brian are working on consistent output data as well. NIST is working with CDC on a similar issues regarding COVID-19 tracking. Inconsistent data quality is an issue for them as well. John G – Nicholas will have some info that will help later during F2F. Move to next F2F.
Oct 8, 2020 - Should be resolved with Pump group and work with Michael Faughn. Move out to January call.
Jan 6, 2021 - Will wrap up when Michael Faughn can focus on it. Review next month.
Feb 3, 2021 - Still working on it - Michael Faughn still working on another project. Move to March. Add 'Containment' to title.
Mar 10, 2021: Michael Faughn still porting Rosetta. Paul wrote a containment model. Pathway figured out, should be able to move forward and use with other devices. Review in May.
April 29, 2021: Coupled with Michael Faughn's availability. Been capturing terms at various workgroup meetings. Set to August meeting.


202 MEMDMC CP to make PID and PV1 segments optional Monroe Pattillo Dalibor, John Rhoads July 7, 2021 Open Apr 25, 2019: MEMDMC profile to change via CP to use a message template of ORU_R(as allocated by O&O) which affords it the ability to make the usage of the PID and PV1 segments as optional for MEMDMC use cases. If PID and/or PV1 segments are present they should be populated per the IHE PCD TF. We did this with ACM, so should be able to do so in MEM.
May 1, 2019: Getting a new trigger event from HL7. We can start testing to this. Won’t make official until HL7 releases new normative. Will need to talk to NIST about flagging this in testing. Set to June TC.
June 5, 2019: Dalibor not here, move to July meeting.
July 10, 2019: Nothing new, move to August.
Aug 7, 2019: HL7 change, NIST tool isn't clear on how to communicate needed info. Add John Rhoads to Participant list.
Sep 4, 2019: Up to HL7 meeting to communicate MEMDMC msg. Conflict in use of PID segment. MEMDMC needs it’s own trigger. Monroe will send to John G for the agenda. Move to October.
Nov 6, 2019: At HL7 O&O. They have a huge backlog, will take time. Problem with HL7 standard, a bit of an unstable reference loop. Is it possible to ‘pre-adopt’ the triggers? Yes, if HL7 says they will create them. Move to Dec.
Dec 4, 2019: Still waiting on HL7. Review in March.
March 4, 2020: Waiting for HL7. In the queue, not discussed yet. Needs a promoter on the committee at HL7 O&O to ensure it’s addressed. John Rhoads will disuss with a member. Move to F2F.
Apr 23, 2020 - Once triggers are officially committed by HL7, they can implement it. Monroe isn’t sure should be actually owner of this. John Rhoads talks to O&O a lot. They have a lot to do with limited resources. He will take ownership. Move to next F2F.
Oct 8, 2020: In HL7 queue, move to February, after HL7 meeting.
Feb 3, 2021 - Need new MEM trigger to avoid PHI info. Move to spring F2F.
April 29, 2021: Passed it into HL7 Orders and Observations, out of their hands now. Has Monroe contacted Hans? John will send his contact to Monroe. Set to June meeting.
June 2, 2021: Monroe sent email to liaison, not reply yet. Move to July.
206


207
208


209


Tracking Related Items, 1-20

Number Item and Relationships Date Added to List Date Closed Description/Update
1

VA proposal on PulseOx - write up details / issues to TC (Ioana S./Greg S.). Provide mappings to x73 of what VA has from LOINC & SNOMED CT - VA to encode (encode all information?)

F2F Oct. 2011
2

DCM (Detailed Clinical Model for Devices) - Develop/provide a publication in a form that will be given to IHE-PCD (Ioana S.) due

F2F Oct. 2011 Oct 5, 2017 Oct 5, 2017: Reviewed at F2F. Unanimous decision by TC to sunset this item.
3 SFT Segment - Desire to include info from pumps, software segment preferred. F2F April 12, 2018
4
5
6
7
8


9


10


11
12
13
14
15
16
17
18


19


20


Tracking Related Items, 21-40

Number Item and Relationships Date Added to List Date Closed Description/Update
21
22
23
24
25
26
27
28


29


30


See also PCD Technical Committee Closed Action Items page.

Links to PCD TC Meetings

Go to most recent/past meetings or next meeting Category: PCD Meeting

Patient Care Device home