national readiness and orchestration patterns june 24, 2015 architecture, services, and apis arien...
TRANSCRIPT
![Page 1: National Readiness and Orchestration Patterns June 24, 2015 Architecture, Services, and APIs Arien Malec, co-chair David McCallie, co-chair](https://reader037.vdocuments.site/reader037/viewer/2022100501/56649d705503460f94a52074/html5/thumbnails/1.jpg)
National Readiness and Orchestration Patterns
June 24, 2015
Architecture, Services, and APIs
Arien Malec, co-chairDavid McCallie, co-chair
![Page 2: National Readiness and Orchestration Patterns June 24, 2015 Architecture, Services, and APIs Arien Malec, co-chair David McCallie, co-chair](https://reader037.vdocuments.site/reader037/viewer/2022100501/56649d705503460f94a52074/html5/thumbnails/2.jpg)
ASA Workgroup - Active Members
2
Name Organization
David McCallie, co-chair Cerner
Arien Malec, co-chair RelayHealth Clinical Solutions
Janet Campbell Epic
George Cole Allscripts
Josh Mandel Children's Hospital Boston
Jeff Gunther Premier, Inc.
Gajen Sunthara, ex officio Department of Health and Human Services (HHS)
Albert Bonnema Defense Health Agency
Debbie Bucci, staff lead HHS, Office of the National Coordinator
![Page 3: National Readiness and Orchestration Patterns June 24, 2015 Architecture, Services, and APIs Arien Malec, co-chair David McCallie, co-chair](https://reader037.vdocuments.site/reader037/viewer/2022100501/56649d705503460f94a52074/html5/thumbnails/3.jpg)
3
Standard Readiness
• HL7 FHIR– not ready for national standard (but on the cusp)– usage encouraged as part of the functional requirement in NPRM
• Healthcare Provider Directory (HPD)– not ready for national standard– should be removed from NPRM
• XDM Package Processing– general agreement - with slight modifications
• Continuity of Care Document (CCD) – Limit to CCD for Data Portability
• CAQH CORE – Should NOT be in the NPRM – Limit to CAQH processing – Rule should be limited to receivers not senders because concern information may
lost when trying to conform to the standard – Need to accommodate for Suffix
![Page 4: National Readiness and Orchestration Patterns June 24, 2015 Architecture, Services, and APIs Arien Malec, co-chair David McCallie, co-chair](https://reader037.vdocuments.site/reader037/viewer/2022100501/56649d705503460f94a52074/html5/thumbnails/4.jpg)
4
Potential Task Force – Orchestration Patterns
• Peer to Peer and Peer to Peer with delegated auth – Likely covered by Argonaut project
• Publish –Subscribe – General pattern notification of an event
• Clinical Decision Support as a Service – Example of more generalize orchestration patterns– Workflow triggered call to outside services– Background Conversation – – Human Review Conversation– Return recommendations - content– IHE related publication example of specific implementation