Difference between revisions of "PCD Technical Committee Action Items"

From IHE Wiki
Jump to navigation Jump to search
m (→‎Items 90-99: partial updates with movement of closed items to other page)
m (rev)
 
(504 intermediate revisions by 6 users not shown)
Line 5: Line 5:
 
Significant recent changes, other than dates, will be in bold.
 
Significant recent changes, other than dates, will be in bold.
  
==Items 60 - 69==
+
==Items 60 - 69 Are Closed ==
  
:{|border="2"
+
==Items 70-79 Are Closed==
|-
 
! width="5%"  align="center" |Number
 
! width="15%"  align="left"  |Action
 
! width="5%"  align="left"  |Owner
 
! width="15%"  align="left"  |Participants
 
! width="5%"  align="left"  |Due Date
 
! width="5%"  align="left"  |Status
 
!              align="left"  |Comments
 
  
|-
+
==Items 80-89 are closed==
| align="center" | 60
 
| '''<Action Item>''' |Update TF
 
| '''<Owner>:'''  |Todd, Ken
 
| '''<Participants>''' | John Rhoads
 
| '''<Due Date>'''  | 2011.04.27
 
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  | Previous history is available on this Wiki (see history tab).
 
  
The update will include PIB, SPD. Todd will ask the IHE Cochairs if the format must be changed to the new format or can be left as is. A format change to the TF is anticipated. This would place the boiler plate into volume 0. Manny to develop the essential elements of the Integration Statements and check to see if the requirement for PCD-01 from the DOR to the DOF is clearly written. Robert is leading a group addressing the issues with PAM ITI-30 and 31. Paul noted that web services will provide additional benefits such as security. The profile updates to HL7 v 2.6 will be folded in. Dec. 9, 2009: Change date to Dec. 18. John Garguilo noted Bikram’s observation about OBR field lengths. He recommended discussion and decision, perhaps using RE for those not used. Paul noted that there will be CPs coming out of coordination with Continua. Feb. 24, 2010: Updating TF is in progress, addressing non-controversial items. A draft of Volume 2 will be available shortly. Volume 3, delayed, will contain much of what was in Volume 2. CPs for Continua harmonization will be incorporated before the revised TF is issued for ballot. June 30, 2010: Change date to Sept. 15. September 22, 2010: Todd is working on TF Volume 3 which will include what was Volume 2 Appendix D. Manny to ask Todd for a potential date. '''April 6, 2010: Change due date to April 27 and note open ballot. John Rhoads noted that one more CP regarding OBX-18 may come in response to the ballot. Then a new TI version will be developed with items not yet ready for FT. '''
+
==Items 90-99 are closed==
 
 
|-
 
| align="center" | 66
 
| '''<Action Item>''' | HL7 IHE-PCD Integration (Message) Profiles (i.e., Message Workbench [MWB] profiles)
 
| '''<Owner>:'''  | John Garguilo
 
| '''<Participants>''' | Al Engelbert, Todd Cooper, Robert Flanders.
 
| '''<Due Date>'''  | 2011.05.31
 
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  | Previous history is available on this Wiki (see history tab).
 
  
Gary volunteered to develop and maintain MWB profiles for three profiles, including tables (data type and others); initial versions are available and can be enhanced for future (cycles) use. Gary is maintaining MWB profiles and NIST bases/develops their message context validation files based on the MWB HL7 profiles.  Volunteers are requested to help on the other profiles (ACM PCD-04 through 08). For ACM, Monroe indicated that only PCD-04 is currently stable. Gary will work on PCD-04 as well. Manny will talk with Nick regarding IDCO (for PCD-09). Gary noted that the MWB tool permits building the message, while that is not available in the NIST tools. John Garguilo noted that the MWB also provides the capability to execute (or simulate) a sending/receiving system for testing. NIST is working on building Test Agents to achieve similar functionality and John will provide updates as the Agents are written in software. September 22, 2010: John Garguilo will ask members to take responsibility for maintaining the profiles and keep the latest version on the ftp site. Companies will be able to constrain these further. Gary will lead an effort to coordinate this. Manny indicated that the MWB and Peter Rontey’s tutorial are posted on the ftp site. If any changes are required members should send Manny an email. Peter has limited time available because his responsibilities have changed. He may have room in an upcoming tutorial but is not offering tutorials regularly. '''April 6, 2010: John Garguilo suggested that this will be less of an issue with further development of NIST tools. John Garguilo will take the lead and attempt to gather the latest versions. He noted that Peter Rontey is unable to maintain the tool, but it may still be useful as a system to test against until the NIST tool provides that service. Al noted that another use for the MWB is to have a local system. John Rhoads suggested that it also provides useful reports. HL7 continues to recognize the MWB as a tool. Al asked if the NIST tool will produce an XML conformance profile. The NIST tools will accept XML profiles and might provide the conformance profile to use in the MWB. This will permit the MWB profiles to be updated in synch with NIST updates. John Rhoads suggested that GForge be used for version control. Date changed to May 31. '''
+
==Items 100-109 are closed==
  
|}
+
==Items 110-119 are closed==
  
==Items 70-79==
+
==Items 120-129 are Closed==
  
 
:{|border="2"  
 
:{|border="2"  
 
|-
 
|-
! width="5%"  align="center" |Number
 
! width="15%"  align="left"  |Action
 
! width="5%"  align="left"  |Owner
 
! width="15%"  align="left"  |Participants
 
! width="5%"  align="left"  |Due Date
 
! width="5%"  align="left"  |Status
 
!              align="left"  |Comments
 
  
  
 
|}
 
|}
  
==Items 80-89==
+
==Items 130-139 are closed==
  
:{|border="2"
+
==Items 140-149 are Closed==
|-
 
! width="5%"  align="center" |Number
 
! width="15%"  align="left"  |Action
 
! width="5%"  align="left"  |Owner
 
! width="15%"  align="left"  |Participants
 
! width="5%"  align="left"  |Due Date
 
! width="5%" align="left"  |Status
 
!              align="left"  |Comments
 
  
 +
==Items 150-159 are Closed==
  
 +
==Items 160-169 are Closed==
  
|-
+
==Items 170-179 are Cosed==
| align="center" | 82
 
| '''<Action Item>''' | PCD OIDs & URNs
 
| '''<Owner>:'''  | Todd, John Rhoads
 
| '''<Participants>''' |  John Garguilo
 
| '''<Due Date>'''  | 2011.05.31
 
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  | For history see history tab.
 
 
 
There is an IHE PCD OID page. The IHE Domain Coordination Committee has had a very active discussion re. the management of OIDs within IHE. OIDs will be available when needed. Dec. 9, 2009: Robert reported no news; change to Feb. 4. August 31, 2010: John Garguilo edited action item 67 which needs to follow the management principles established for this action item - 82.  See OID page: [[http://wiki.ihe.net/index.php?title=PCD_OID_Management]]''' April 6, 2011: Refers to IHE GForge. The next step is to document its usage. Change date to May 31. '''
 
  
|}
+
==Items 180-189 are closed==
  
==Items 90-99==
+
==Items 190-199==
  
 
:{|border="2"  
 
:{|border="2"  
 
|-
 
|-
! width="5%"  align="center" |Number
+
! width="5%"  align="center" |No.
! width="15%"  align="left"  |Action
+
! width="15%"  align="left"  |Action Item
 
! width="5%"  align="left"  |Owner
 
! width="5%"  align="left"  |Owner
! width="15%align="left"  |Participants
+
! width="5%   align="left"  |Participants
! width="5%align="left"  |Due Date
+
! width="10%   align="left"  |Due
! width="5%align="left"  |Status
+
! width="5%   align="left"  |Open/Closed
!              align="left"  |Comments
+
!              align="left"  |Description/Update
 +
 
 +
 
  
  
 
|-
 
|-
| align="center" | 93
+
| align="center" | 196
| '''<Action Item>''' | Managing Document Versions
+
| '''<Action Item>''' | Add PCD specific values to HL7 table 78
| '''<Owner>:'''  | John Rhoads
+
| '''<Owner>:'''  | John Garguilo
 
| '''<Participants>''' |  
 
| '''<Participants>''' |  
| '''<Due Date>'''  | 2011.04.31
+
| '''<Due Date>'''  | February 2022
 
| '''<Status>''' |OPEN
 
| '''<Status>''' |OPEN
| '''<Comments>:'''  | F2F:  research the use of GForge. Feb. 24, 2010: John Rhoads to discuss with Steve Moore. June 30, 2010: John R has received approval to use GForge. Change date to Sept. 30, 2010.''' April 6, 2011: The next step is to document its usage. Change date to May 31. '''
+
| '''<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.    HL7write 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 100-109==
+
==Items 200 - 209==
 +
 
  
 
:{|border="2"  
 
:{|border="2"  
Line 118: Line 123:
 
!              align="left"  |Comments
 
!              align="left"  |Comments
  
 +
|-
 +
| align="center" | 202
 +
| '''<Action Item>''' | MEMDMC CP to make PID and PV1 segments optional
 +
| '''<Owner>:'''  | Monroe Pattillo
 +
| '''<Participants>''' | Dalibor, John Rhoads
 +
| '''<Due Date>'''  | February 2022
 +
| '''<Status>''' | Open
 +
| '''<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.
 +
: December 8, 2021. It is "in the queue" with Orders and Observation WG in HL7. Will try again at January HL7 Work Group Meeting to advance it.
  
 
|-
 
|-
| align="center" | 101
+
| align="center" | 206
 
| '''<Action Item>''' |  
 
| '''<Action Item>''' |  
Selection of WCTP by ACM
+
| '''<Owner>:'''  |  
| '''<Owner>:'''  | Monroe
 
 
| '''<Participants>''' |  
 
| '''<Participants>''' |  
| '''<Due Date>'''  | 2010.06.30
+
| '''<Due Date>'''  |  
| '''<Status>''' |OPEN
+
| '''<Status>''' |  
 
| '''<Comments>:'''  |  
 
| '''<Comments>:'''  |  
Initiated F2F May 5, 2010: Todd will seek the MOU for ACM's WCTP.org issue. May 26, 2010: Monroe indicated that WCTP will be used and a CP will be prepared by the WG and submitted to the TC. Todd asked if this will be an option or the single approach. Monroe indicated that both this and SMTP should be accepted and WCTP will be promoted. Todd noted that wired vs. wireless needs to be addressed in the future. CP for ballot and TI available June 30. '''June 30, 2010: Manny to ping Steve Moore about SMTP and WCTP and learn if it is necessary to lose SMTP. Open Action Item for WCTP MOU (PC). Manny to contact Monroe re ballot for WCTP (TC). The question of whether this is a revised supplement or a CP is to be made by the ACM WG. Monroe and Ken will lead the effort. '''
+
 
  
 
|-
 
|-
| align="center" | 102
+
| align="center" | 207
 
| '''<Action Item>''' |  
 
| '''<Action Item>''' |  
Numeric Array (NA) data type
 
 
| '''<Owner>:'''  |  
 
| '''<Owner>:'''  |  
 
| '''<Participants>''' |  
 
| '''<Participants>''' |  
| '''<Due Date>'''  | 2010.06.02
+
| '''<Due Date>'''  |  
| '''<Status>''' |OPEN
+
| '''<Status>''' |  
 
| '''<Comments>:'''  |
 
| '''<Comments>:'''  |
Initiated F2F May 6, 2010: Seek restoration of the Numeric Array (NA) data type. May 26, 2010: Wait to discuss with John Rhoads. Todd noted that HL7 v.7 should go to ballot shortly. The alarm trigger is included. NA could be included in v.2.8. Monroe asked if the TI version of ACM should assume positive ballot on v.7. This should be discussed at the next TC meeting. ''' '''June 30, 2010: Close because John Garguilo believes this data type can be used. '''
 
  
 
|-
 
|-
| align="center" | 105
+
| align="center" | 208
 
| '''<Action Item>''' |  
 
| '''<Action Item>''' |  
Obtain all ADT support required for Connectathon, Showcase
+
| '''<Owner>:'''  |  
| '''<Owner>:'''  | Manny
+
| '''<Participants>''' |  
| '''<Participants>''' | Cochairs
+
| '''<Due Date>'''  |  
| '''<Due Date>'''  | August 4, 2010.
+
| '''<Status>''' |  
| '''<Status>''' |OPEN
+
| '''<Comments>:'''  |
| '''<Comments>:'''  | June 30: Include PAM, PDQ, PEC.
+
 
  
 
|-
 
|-
| align="center" | 106
+
| align="center" | 209
 
| '''<Action Item>''' |  
 
| '''<Action Item>''' |  
PDA
 
 
| '''<Owner>:'''  |  
 
| '''<Owner>:'''  |  
 
| '''<Participants>''' |  
 
| '''<Participants>''' |  
| '''<Due Date>'''  | August 30, 2010.
+
| '''<Due Date>'''  |  
| '''<Status>''' |OPEN
+
| '''<Status>''' |  
| '''<Comments>:'''  |  
+
| '''<Comments>:'''  |
June 30: Possibly to include interim document.
+
 
 +
 
 +
|}
  
 +
==Tracking Related Items, 1-20 ==
  
 +
:{|border="2"
 
|-
 
|-
| align="center" | 108
+
! width="5%"  align="center" |Number
| '''<Action Item>''' | Prioritize Escalated Alarms
+
! width="50%"  align="left"  |Item and Relationships
| '''<Owner>:'''  | Monroe Pattillo
+
! width="5%  align="left"  |Date Added to List
| '''<Participants>''' | ACM WG
+
! width="5%  align="left"  |Date Closed
| '''<Due Date>'''  | December 8, 2010
+
!              align="left"  |Description/Update
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  | Wednesday, Oct. 20: ACM - AC will prioritize alarm and communication when messages are escalated. ACM will add a requirement to notify the person receiving an escalated message that the alarm has been escalated and has an associated delay from the initial alarm. The AC may make decisions on how to prioritize and escalate the message. This may have implications for the AM and perhaps AR.
 
  
 +
|-
 +
| align="center" | 1
 +
| '''<Item and Relationships>''' |
 +
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?)
 +
| '''<Date Added>:'''  | F2F Oct. 2011
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
 +
 +
|-
 +
| align="center" | 2
 +
| '''<Item and Relationships>''' |
 +
DCM (Detailed Clinical Model for Devices) - Develop/provide a publication in a form that will be given to IHE-PCD (Ioana S.) due
 +
| '''<Date Added>:'''  | F2F Oct. 2011
 +
| '''<Date Closed>''' | Oct 5, 2017
 +
| '''<Description/Update>'''  | Oct 5, 2017: Reviewed at F2F.  Unanimous decision by TC to sunset this item.
  
 
|-
 
|-
| align="center" | 109
+
| align="center" | 3
| '''<Action Item>''' | Messages Without Patient Demographics
+
| '''<Item and Relationships>''' | SFT Segment - Desire to include info from pumps, software segment preferred.
| '''<Owner>:'''  | Jeff Rinda
+
| '''<Date Added>:'''  | F2F April 12, 2018
| '''<Participants>''' | Pump WG
+
| '''<Date Closed>''' |  
| '''<Due Date>''' | December 8, 2010
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  | Wednesday, Oct. 20: Pumps (and other devices) sending device data in absence of patient demographics. (PIV initiated, to be discussed in Nov. 17th TC meeting)
 
  
 +
|-
 +
| align="center" | 4
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
  
 +
|-
 +
| align="center" | 5
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
  
|}
+
|-
 +
| align="center" | 6
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
  
==Items 110-119==
+
|-
 +
| align="center" | 7
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
  
:{|border="2"
 
 
|-
 
|-
! width="5%"  align="center" |Number
+
| align="center" | 8
! width="15%"  align="left"  |Action
+
| '''<Item and Relationships>''' |
! width="5%"  align="left"  |Owner
+
| '''<Date Added>:''' |  
! width="15%" align="left"  |Participants
+
| '''<Date Closed>''' |
! width="5%"  align="left"  |Due Date
+
| '''<Description/Update>''' |  
! width="5%" align="left"  |Status
+
 
!              align="left"  |Comments
 
  
 
|-
 
|-
| align="center" | 110
+
| align="center" | 9
| '''<Action Item>''' | WCM Attributes
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  | Paul Schluter
+
| '''<Date Added>:'''  |  
| '''<Participants>''' | Ken Fuchs
+
| '''<Date Closed>''' |  
| '''<Due Date>'''  | December 8, 2010
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
+
 
| '''<Comments>:'''  | Thursday, Oct. 21: Document ways of representing waveform attributes. Ken suggested similar action for PCD-02. To be discussed Nov 3rd TC meeting.
 
  
 
|-
 
|-
| align="center" | 111
+
| align="center" | 10
| '''<Action Item>''' | New Born Hearing Terminology
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  | Nitin Kunte
+
| '''<Date Added>:'''  |  
| '''<Participants>''' | Paul Schluter, John Garguilo
+
| '''<Date Closed>''' |  
| '''<Due Date>'''  | January 5, 2011
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
+
 
| '''<Comments>:'''  | Tuesday, Dec. 7: Discussion to include proposed new terminology in a systematic and consistent way via the RTM Integration Profile.
 
  
 
|-
 
|-
| align="center" | 112
+
| align="center" | 11
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |  
+
| '''<Date Closed>''' |
| '''<Due Date>'''  |  
+
| '''<Description/Update>'''  |
| '''<Status>''' |OPEN
+
| '''<Comments>:'''  |
+
|-
 +
| align="center" | 12
 +
| '''<Item and Relationships>''' |  
 +
| '''<Date Added>:'''  |  
 +
| '''<Date Closed>''' |  
 +
| '''<Description/Update>'''  |  
  
 
|-
 
|-
| align="center" | 113
+
| align="center" | 13
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 114
+
| align="center" | 14
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 +
|-
 +
| align="center" | 15
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
  
 
|-
 
|-
| align="center" | 115
+
| align="center" | 16
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |  
 
  
 
|-
 
|-
| align="center" | 116
+
| align="center" | 17
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 117
+
| align="center" | 18
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |  
+
| '''<Date Closed>''' |  
| '''<Due Date>'''  |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
+
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 118
+
| align="center" | 19
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |  
+
| '''<Date Closed>''' |  
| '''<Due Date>'''  |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
+
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 119
+
| align="center" | 20
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
  
Line 293: Line 348:
 
|}
 
|}
  
==Items 120-129==
+
==Tracking Related Items, 21-40 ==
  
 
:{|border="2"  
 
:{|border="2"  
 
|-
 
|-
 
! width="5%"  align="center" |Number
 
! width="5%"  align="center" |Number
! width="15%"  align="left"  |Action
+
! width="50%"  align="left"  |Item and Relationships
! width="5%"  align="left"   |Owner
+
! width="5%  align="left"  |Date Added to List
! width="15%"  align="left"  |Participants
+
! width="5%   align="left"  |Date Closed
! width="5%align="left"  |Due Date
+
!              align="left"  |Description/Update
! width="5%"  align="left"  |Status
 
!              align="left"  |Comments
 
  
 
|-
 
|-
| align="center" | 120
+
| align="center" | 21
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |  
+
| '''<Date Closed>''' |
| '''<Due Date>'''  |  
+
| '''<Description/Update>'''  |
| '''<Status>''' |OPEN
+
| '''<Comments>:'''  |  
+
|-
 +
| align="center" | 22
 +
| '''<Item and Relationships>''' |  
 +
| '''<Date Added>:'''  |  
 +
| '''<Date Closed>''' |  
 +
| '''<Description/Update>'''  |  
  
 
|-
 
|-
| align="center" | 121
+
| align="center" | 23
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 122
+
| align="center" | 24
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 123
+
| align="center" | 25
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 124
+
| align="center" | 26
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 +
|-
 +
| align="center" | 27
 +
| '''<Item and Relationships>''' |
 +
| '''<Date Added>:'''  |
 +
| '''<Date Closed>''' |
 +
| '''<Description/Update>'''  |
  
 
|-
 
|-
| align="center" | 125
+
| align="center" | 28
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |  
 
  
|-
 
| align="center" | 126
 
| '''<Action Item>''' |
 
| '''<Owner>:'''  |
 
| '''<Participants>''' |
 
| '''<Due Date>'''  |
 
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 127
+
| align="center" | 29
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
|-
 
| align="center" | 128
 
| '''<Action Item>''' |
 
| '''<Owner>:'''  |
 
| '''<Participants>''' |
 
| '''<Due Date>'''  |
 
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
 
|-
 
|-
| align="center" | 129
+
| align="center" | 30
| '''<Action Item>''' |  
+
| '''<Item and Relationships>''' |  
| '''<Owner>:'''  |  
+
| '''<Date Added>:'''  |  
| '''<Participants>''' |
+
| '''<Date Closed>''' |  
| '''<Due Date>''' |  
+
| '''<Description/Update>'''  |  
| '''<Status>''' |OPEN
 
| '''<Comments>:'''  |
 
  
  
  
 
|}
 
|}
 +
 +
See also [[PCD Technical Committee Closed Action Items]] page.
  
 
=='''Links to PCD TC Meetings'''==
 
=='''Links to PCD TC Meetings'''==
Line 406: Line 442:
  
 
[[Category:PCD]]
 
[[Category:PCD]]
 +
[[Category:PCD Reference Pages]]

Latest revision as of 10:31, 12 January 2022

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 February 2022 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
202 MEMDMC CP to make PID and PV1 segments optional Monroe Pattillo Dalibor, John Rhoads February 2022 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.
December 8, 2021. It is "in the queue" with Orders and Observation WG in HL7. Will try again at January HL7 Work Group Meeting to advance it.
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