All
Accepted answers
Kurt Dawn · Oct 18, 2019 go to post

Using the Installer Wizard to create a foundation production and namespace provides you with a base production with all the mappings needed for a healthcare interoperability production. It saves you the time and effort of creating your own namespace and production needed for healthcare interoperability. You do not always have to start with a foundation production; if you are comfortable creating your own namespace and production, you can do so.  As a side note, when you create an HL7 production, you are creating a foundation production.

The Ens.Activity.Operation.Local operation is used for activity monitoring. It is not required by the foundation production. For more about activity monitoring, see https://docs.intersystems.com/healthconnect20191/csp/docbook/DocBook.UI.Page.cls?KEY=EMONITOR_activity
.

Kurt Dawn · Jan 3, 2019 go to post

The InterSystems documentation does not currently contain examples of creating FHIR / HL7v2 transformations. We will consider this for future releases. Information about FHIR Release 3 (STU) is included in the latest documentation.

Kurt Dawn · Feb 14, 2019 go to post

The recommended method of transforming data from CCD to HL7 is to use InterSystems SDA as an intermediary format. Use pre-built XSLTs to convert from CDA to SDA , and then create a DTL transformation to map the SDA to HL7. Here are the names of some related books:

  • CDA Interoperability with SDA
  • The InterSystems Clinical Data Model: SDA (in future releases, this will be renamed to "SDA: InterSystems Clinical Data Format")
  • Developing DTL Transformations
Kurt Dawn · Aug 17, 2020 go to post

As the 2020.3 FHIR server supports the core R4 FHIR specification, you can find the StructureDefinitions in two ways: