Details
-
Type:
Change Request
-
Status: Applied (View Workflow)
-
Priority:
Highest
-
Resolution: Persuasive
-
Specification:US FHIR Guidance - Quality Reporting (FHIR)
-
Raised in Version:0.1
-
Work Group:Clinical Quality Information
-
Related Page(s):Home
-
Related Section(s):Aignment
-
Grouping:
-
Resolution Description:
-
Resolution Vote:Rob Samples/Floyd Eisenberg: 19-0-1
-
Change Category:Clarification
-
Change Impact:Non-substantive
Description
Please explain in which cases one needs to provide this transformation logic. So it sounds like if all is done with FHIR then it is already aligned with the existing clinical systems. Do you then oppose this to non FHIR implementations that may not be aligned and thus would need an additional data transforming adapter layer? This is a bit arguable then, as other solutions may also be aligned with the existing clinical information systems. So Probably here you mean that because of this existing alignment of FHIR if one uses FHIR then there is no need to writing transformation logic?
Existing Wording:
The less transformation logic has to be written
Proposed Wording:
?
Attachments
Issue Links
- is voted on by
-
BALLOT-12629 Affirmative - Javier Espina : 2020-May-QUALREPORT R1 Inform
- Balloted