POCUS PC Checkpoint Assessment

Annex: PC-Prep Closing Assessment

Paste the following checklist items into the minutes; discuss and record findings for each

• Profile Name: EBIW POCUS Extensions
• Did we line-by-line the entire document: No
  • Need to line-by-line
    • Vol1: 2 concepts (Billing, Intermittent Connected Modalities), 3 more use cases and Data model
    • Vol2: RAD-132
• How ready is it to go out for PC: Completely, Almost, Soonish, Hmmm: Almost
• Which open issues are risky, and why: Identification of training studies needs to be better vetted with ACEP
• Are all open issues phrased to solicit the needed information to close them? Yes
• Which use cases need more input None
• Which issues from the Kickoff Closing Assessment are still unresolved Need to finish line by line
• What significant debates in PC-prep were not anticipated in the Kickoff
  • Revisiting whether or not to create a separate profile, and / or whether or not to create a "POCUS Encounter Manager"
  • Lots of time spent trying to get the Actor diagram into IHE format
• Review ALL "uncertainty points" in the evaluation. Are all now resolved?
  • Packaging (profile vs EBIW extension): Resolved - after another debate, TC agreed to stick with original decision to keep the POCUS Option in EBIW
  • Finalize Actors (especially organization of POCUS management functions): RESOLVED
  • Draft Transaction: Store Report (i.e., Store the POCUS procedure report. An HL7v2 ORU^R01 modeled after RAD-128): decided to incorporate ORC segments in existing RAD-132. Still needs Line-by-line
  • RAD-130: ADT mapping of HL7 Visit Number (PV1-19) to Admission ID (0038,0010) for Encounter linking as a concept: Not an ENcounter Manager Requirement, but mapped in Informative Annex and included in Concept section "47.4.1.5 Obtaining Encounter Metadata"
  • R+ Physician of Record (Attending) in Visit Admission Module (DICOM cp2451): Reviewed in Line-by-line
  • RAD-131: R+ Physician of Record"
  • Reporting (and relation to imaging reports, clinical notes, etc.)
• Review ALL "complexity points" in the evaluation. Did each get appropriate text coverage/resolution?
• Review the "effort points" in the evaluation. Still seems right? Need more?
• How does the scope feel in terms of being a useful chunk of work? (Needs more? Just right? More than enough?)
• How is the work fitting in the allocated bandwidth? (Time to spare? Just right? Things were left undone?)
• Did the Breakdown of Tasks accurately reflect the work? What extra tasks arose?
• Looking forward, if you had to reduce scope to hit TI, what would you drop
• Have the promised resources manifested
• What vendors are engaged (for each actor)
• When will we have sample data/objects
• Who should specifically be targeted for Public Comment feedback
• Was the profile where it needed to be at the start of the PC meeting (See "PC Prep Meeting" above), if not what was the gap
• Was the profile where it needed to be at the end of the PC meeting, if not what was the gap
• How many tcons would you like between now and PC Publication
• Do you need any tcons before TI Prep Meeting