vault backup: 2024-12-23 08:25:00

fastenhealth · Dec 23, 2024 · 8a38ddd · 8a38ddd
1 parent c69c49e
commit 8a38ddd
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 4 deletions.
diff --git a/.obsidian/workspace.json b/.obsidian/workspace.json
@@ -13,12 +13,12 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "getting-started/sandbox.md",
+                "file": "legal/information-blocking-faqs.md",
                 "mode": "source",
                 "source": false
               },
               "icon": "lucide-file",
-              "title": "sandbox"
+              "title": "information-blocking-faqs"
             }
           },
           {
@@ -212,8 +212,9 @@
       "command-palette:Open command palette": false
     }
   },
-  "active": "8360a188f8a1d092",
+  "active": "5fc1dd549bcf0f60",
   "lastOpenFiles": [
+    "getting-started/sandbox.md",
     "getting-started/index.md",
     "legal/21st-century-cures-act.md",
     "legal/carin-trust-framework.md",
@@ -239,7 +240,6 @@
     "providers/flexpa-supported-payers.md",
     "providers/index.md",
     "providers/largest-ehr-platforms.md",
-    "providers/largest-healthcare-companies.md",
     "banner-transparent.png",
     "getting-started/img.png",
     "img/sponsors/browserstack.png",

diff --git a/legal/information-blocking-faqs.md b/legal/information-blocking-faqs.md
@@ -131,6 +131,9 @@ From Regulation text at § 170.404(A)(2)
 
 ## Charging Fees for Patient Access Apps would be Information Blocking
 
+Please be advised that developers of Certified Health IT, may not charge a fee to application developers (“API Users”) requesting access to their Certified Patient Access APIs. Doing so would violate the Conditions and Maintenance of Certification for Patient Access APIs of the 21st Century Cures Act (45 CFR 170.404). The only fees a Certified API Developer is permitted to charge to an API User are for “value-added services related to certified API technology, so long as such services are not necessary to efficiently and effectively develop and deploy production-ready software that interacts with certified API technology.”
+
+
 Couple more explicit examples where Fees would qualify as information blocking:
 
 [https://www.federalregister.gov/d/2020-07419/p-1315](https://www.federalregister.gov/d/2020-07419/p-1315)  
@@ -148,6 +151,8 @@ Couple more explicit examples where Fees would qualify as information blocking:
 
 > For example, a health care provider that charges individuals a fee in order for the individuals to receive access to their EHI via the health care provider's patient portal or another internet-based method, would not be able to benefit from this exception. Similarly, **where an individual authorizes (approves) a consumer-facing app to receive EHI on the individual's behalf, the exception would not apply** to practices where an actor charges the app or its developer a fee to access or use APIs that enable an individual's access to the individual's EHI.
 
+
+
 ## Sandbox for Testing
 
 TODO: