# Structured Reporting
**URL:** https://discourse.orthanc-server.org/t/structured-reporting/1749
**Category:** Google Groups archive
**Created:** [January 7, 2020, 5:25pm UTC](https://discourse.orthanc-server.org/t/structured-reporting/1749 "2020-01-07T17:25:16Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@John\_Hearns](https://discourse.orthanc-server.org/u/John_Hearns)
#### Post date: [January 7, 2020, 5:25pm UTC](https://discourse.orthanc-server.org/t/structured-reporting/1749/1 "2020-01-07T17:25:16Z")
A very quick question please. I am considering using Orthanc.
I have been asked if it supports Structured Reporting.
Thanks, John Hearns
---
### Author:  [@jodogne](https://discourse.orthanc-server.org/u/jodogne)
#### Post date: [January 7, 2020, 7:27pm UTC](https://discourse.orthanc-server.org/t/structured-reporting/1749/2 "2020-01-07T19:27:56Z")
As written in the Orthanc Book, Orthanc can receive/store/transmit DICOM-SR (structured reports):
[https://book.orthanc-server.com/faq/supported-images.html](https://book.orthanc-server.com/faq/supported-images.html)
The analysis of DICOM-SR can be done through Lua scripts, through plugins; through external scripts using the JSON format, or from external DICOM viewers.
---
### Author:  [@boskar](https://discourse.orthanc-server.org/u/boskar)
#### Post date: [January 26, 2020, 8:57pm UTC](https://discourse.orthanc-server.org/t/structured-reporting/1749/3 "2020-01-26T20:57:32Z")
As parsing DICOM headers is quite awful Orthanc helps here a lot as You can parse the json version - that’s what I did in my project.
W dniu wtorek, 7 stycznia 2020 18:25:16 UTC+1 użytkownik John Hearns napisał:
---
### Author:  [@Dominic\_Bou-Samra1](https://discourse.orthanc-server.org/u/Dominic_Bou-Samra1)
#### Post date: [January 27, 2020, 10:33pm UTC](https://discourse.orthanc-server.org/t/structured-reporting/1749/4 "2020-01-27T22:33:04Z")
I use Orthanc for an application that relies heavily on the contents inside structured reports. I ended up writing a parsing layer than transforms the contents into values that make sense inside my domain (measurements, findings etc). I make use of the JSON output Orthanc emits.
---
### Author:  [@Deepak\_Tiwari](https://discourse.orthanc-server.org/u/Deepak_Tiwari)
#### Post date: [May 29, 2022, 7:30pm UTC](https://discourse.orthanc-server.org/t/structured-reporting/1749/5 "2022-05-29T19:30:11Z")
Please Explain How To Extract our Required Data into Json Format from SR Reports
---
### Author:  [@Deepak\_Tiwari](https://discourse.orthanc-server.org/u/Deepak_Tiwari)
#### Post date: [May 29, 2022, 7:31pm UTC](https://discourse.orthanc-server.org/t/structured-reporting/1749/6 "2022-05-29T19:31:27Z")
Please Explain How To Extract our Required Data into Json Format from SR Reports
thanks
---
### Author:  [@alainmazy](https://discourse.orthanc-server.org/u/alainmazy)
#### Post date: [May 30, 2022, 9:01am UTC](https://discourse.orthanc-server.org/t/structured-reporting/1749/7 "2022-05-30T09:01:27Z")
Hi,
Once you have the id of an instance, you can get a json version of all DICOM Tags through the /tags endpoint:ex: [http://localhost:8042/instances/18845bf1-671a1dc2-4162f04d-b1b39f1c-282474e0/tags?simplify](http://localhost:8042/instances/18845bf1-671a1dc2-4162f04d-b1b39f1c-282474e0/tags?simplify)
DICOM SRs are just made of DICOM Tags so you get the full SR content there.
HTH
Alain.