Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
-
1.0.0
-
Public Health
-
Knowledge Artifact Repository
-
3.2.3
-
-
Nagesh Bashyam/Bill Lober : 10-0-2
-
Correction
-
Compatible, substantive
-
1.0.0
Description
Is it expected that other actors, like the HDEA, will interact with the Knowledge Artifact Repository and process a PlanDefinition or StructureDefinition on the fly/at run-time and without prior knowledge of the expectations of the use case? Or will these expectations be fully defined at the time of onboarding so that the HDEA can be designed accordingly? If the former, this puts a tremendous, and possibly unrealistic, burden on the components on the healthcare organization/EHR side to perform dynamically. We request that the expectations of the actors be more clearly defined, accounting for burden on sending system.
Attachments
Issue Links
- mentioned in
-
Page Loading...