IHE #FHIR profiles - MHD, PDQm, and PIXm

The IHE IT Infrastructure committee has a few profiles on #FHIR. They just published new revisions  (see below) that have aligned on DSTU2, formerly on pre-DSTU2 versions. They have also just published for Public Comment a new set of supplements. All of these are aligned with DSTU2. When STU3 finishes ballot and publishes reconciled version, then IHE will adjust all of these to STU3.

Read more »

Comments

Post a Comment

Popular posts from this blog

Certificate validation - use of CN

Image
I got a question of what should be done with the Certificate CN (common name) value. Specifically should a system make sure that the TCP/IP Connection aligns with the CN hostname value? The short answer is: ignore the Certificate CN; as the TLS authentication mechanism has already done cryptographically secure authentication. Adding any use of DNS to this will only result in false-negatives, meaning it will never add value but will occasionally cause you to reset a perfectly good connection. Here is the question: I have been trying to understand the certificate requirements in ITI-TF 2,  3.19.6.13 (Other Certificate Requirements) especially: "The Secure Node shall not require any specific certificate attribute contents, nor shall it reject certificates that contain unknown attributes or other parameters.   Note that for node certificates the CN often is a host name, attempting to use this host name provides no additional security and will introduce a new failure mode (e.g., DN...
Read more

Controlling Big-Data feeding frenzy with Privacy Consent Authorization

Image
This is a start of a series of articles on the various Privacy Consent mechanisms that are being developed in HL7, IHE, and HEART . I will describe them quickly, but will go into more detail in later articles. Big Data Feeding Frenzy This is what most people think of when they hear about healthcare data in the context of "Big Data".  This diagram shows a very minimal "Privacy Consent". One that only controls if the Patients data is available or NOT. Too often this is refereed to as OPT-IN, or OPT-OUT. This is a mischaracterization, but it is one that must be addressed.  This kind of configuration does happen. I am not saying it doesn't happen. Just that it shouldn't be confused with OPT-IN, or OPT-OUT. I know that I will not succeed in defining OPT-IN or OPT-OUT. They have too much momentum behind poor definitions. I did try to add clarity in the FHIR Consent " General Model " section. Consent Controlled Feeding First step is to recognize that Pr...
Read more

Consent to grant read access to a specific types of FHIR Resource

Image
Grahame got this question on FHIR Consent , and forward it to me to answer. Question: I am using the FHIR Contract resource ( https://www.hl7.org/fhir/contract.html ) to convey the patient consent for a provider to access specific FHIR resources (Ex: Observation, MedicationOrder, DiagnosticReport…). Which field in the Contract resource can be used to specify the list of consented FHIR resources? The short answer is that today this is unclear as there are many ways to do it. This is a problem that I struggle with and intend to use this blog article to help narrow the solution space so as to make progress in the modeling. The Privacy Consent Directive (PCD) Implementation Guide is where the CBCC and Security workgroups are building the solution. We are making progress, but not as much as I would like. We tend to spend far too much time re-arranging the chairs, and too little time making solutions. I like the Question, as it gives a concrete thing to focus on. Background  I cover th...
Read more