← Prev in month
← Prev in thread
Next in thread →
Next in month →
FW: JPATS TEP requirements
Folks, an FYI. Per recent email updates we’re continuing a process to ensure that federal partners on the HHS side are fully on board with TEP, and recent events have put the effort squarely back on the map. Although we have in fact performed a successful TEP patient tracking exercise with JPATS in 2010, and requirements were modified somewhat based upon that experience, they have not been as closely engaged as we would like. So below is meant to re-engage to specifically validate our requirements or identify any outstanding issues to be addressed by our SC. JPATS purpose can basically be compared to FedEx or UPS – “getting and tracking a package from point A to B to C”. Though they do carry basic information about the patient status such as “triageStatus”, they do not deal with other elements that the state and local stakeholders care about. Please let me know if you have any questions. Thanks, Tim Tim Grapes SE Solutions, Inc. (703) 304-4829 From: Grapes, Timothy Sent: Thursday, November 10, 2011 9:42 AM To: Knell, Charles (HHS/ASPR/OPEO) Cc: Britt, Darryl (HHS/ASPR/OPEO) Subject: RE: JPATS double check of requirements Sounds good Chuck. Let’s touch base next week and exchange that information – you provide the JPATS elements, and we provide and also analyze currently proposed mandatory elements against that to resolve any potential issues so that JPATS can use the data exchange without dealing with required elements that would be invalid to you. Thanks – have a good weekend guys, Tim Tim Grapes SE Solutions, Inc. (703) 304-4829 From: Knell, Charles (HHS/ASPR/OPEO) [mailto:] Sent: Thursday, November 10, 2011 8:56 AM To: Grapes, Timothy Cc: Britt, Darryl (HHS/ASPR/OPEO) Subject: Re: JPATS double check of requirements Tim, The spreadsheet with the data elements would be great. Since the data requirements in jpats are small I would also be conserned with required TEP elements that might not be captured or required in jpats. I am out of the office today but maybe we could touch base early next week. Hope all is well. Sent from my iPhone On Nov 10, 2011, at 8:48 AM, "Grapes, Timothy" <> wrote: Darryl and Chuck, Hope things are well. As we move forward with TEP in OASIS in coordination with HL7, I’d like to touch base with you to determine the most effective way to perform a “double-check” to ensure we have addressed all JPATS information needs for sharing of patient movement information with other systems, as well as data you expect other systems to share with you during patient movement. The goal would be for both you and us to be fully confident that the standard requirements do in fact cover all of your current or planned information needs. In addition, Joe with MD, TN and LA is planning to incorporate a demo in with their panel during the May summit, and this gives us the opportunity to perform any necessary tweaks prior. I can think of a couple ways to go about this to respect your time and priorities, and would like to offer that we do the leg work, and then perhaps do a quick sit-down with you to confirm results of mapping your info needs with requirements captured. One thought is; I know that you have provided excel or other formats to partners during exercises for upload/download - if you have that information handy you could initially send us that list of data elements in whatever format you have, so that we can map and compare with our requirements captured. We could also sit down in the beginning to walk it through, but I think it would take less of your time if we could do the initial work and come forward with the results for your review. Let me know what you think, or give me a call. Thanks, Tim Tim Grapes SE Solutions, Inc. (703) 304-4829 No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1869 / Virus Database: 2092/4607 - Release Date: 11/09/11 No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1869 / Virus Database: 2092/4607 - Release Date: 11/09/11
← Prev in month
← Prev in thread
Next in thread →
Next in month →