Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>MedCom Firely ValidationNew to Visual Studio Code? Get it now.
MedCom Firely Validation

MedCom Firely Validation

MedComPublisher

|
4 installs
| (0) | Free
Firely validation and live narrative preview for FHIR implementation guides.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

MedCom Firely Validation

Choose either command from the Command Palette or by right-clicking sushi-config.yaml:

  • Build and Validate: the existing quick Firely Terminal validation of generated Bundles. Choose whether to run SUSHI and delete old Publisher output.
  • Validate with SDK: validates published output/Bundle-*.json and output/Bundle-*.xml against output/package.tgz using the Firely .NET SDK (FHIR R4). Select Run _genonce.sh (checked by default) to rebuild first, or clear it to use the existing package and published resources.

When selected, the extension runs bash ./_genonce.sh in the open workspace folder containing the selected guide. The script handles its own Publisher configuration and build prerequisites. A failed script or missing new package stops validation. When cleared, the script is not required and output/package.tgz is preserved. Both the package and Bundles are read from that workspace folder’s output directory, including narratives generated by Publisher. If the package is missing, validation stops before tool setup with its expected path and instructions to select Run _genonce.sh. Missing published Bundles also stop validation with instructions to rebuild. The SDK path does not require Firely Terminal.

Errors appear in Problems, linked to JSON nodes where a location is available. XML errors are linked to the file, with resource paths in the diagnostic message. Full errors and warnings appear in the MedCom Firely Validation output channel. JSON and XML copies are validated separately and each counts toward the result. Quick Terminal validation still reads fsh-generated/resources; it reports a warning when no Bundles are found.

The setup task installs missing .NET SDK 8, npm, and SUSHI in your user directory, plus Firely Terminal for quick validation. The SDK validator restores its NuGet dependencies on first use. FHIR package dependencies use the local FHIR cache and package server; terminology validation tries local definitions, MIME types, then https://tx.hl7europe.eu/r4. Network access may be needed.

Settings:

  • fhirIg.firelyPath: Firely Terminal executable for quick validation (default fhir).
  • fhirIg.sushiPath: SUSHI executable for quick validation (default sushi).
  • fhirIg.dotnetPath: .NET SDK executable (default dotnet).
  • fhirIg.terminologyServer: fallback FHIR R4 terminology endpoint for SDK validation.

For faster SDK runs, clear Run _genonce.sh to reuse the published output. This validates the last build; rebuild after changing profiles or instances. See narrative generation options for the limits of reducing Publisher work.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft